[Puppet-users] Mount and fstab problems with large devices?

[Mike Renfro]

I'm trying to get a new file server managed by puppet from day 1, at 
least as much as possible. At the moment, though, there's two issues I'm 
running into:

1. fstab should have entries for my comically-large RAID, but doesn't.
2. each puppet run appears to remount the RAID, even when no rules in 
the manifest change.

I suspect the issue may be in parsing 'df' output in provider/mount.rb, 
but I'm not sure. Two puppet runs, one right after the other, both show 
output including:

debug: Mount[/home/CAE](provider=parsed): Executing '/bin/df'
debug: //ch208r/Mount[/home/CAE]: Changing device,fstype
debug: //ch208r/Mount[/home/CAE]: 2 change(s)
notice: //ch208r/Mount[/home/CAE]/device: defined 'device' as 
'/dev/mapper/md1000-home'
notice: //ch208r/Mount[/home/CAE]/fstype: defined 'fstype' as 'xfs'
debug: Flushing mount provider target /etc/fstab
notice: //ch208r/Mount[/home/CAE]: Refreshing self
info: Mount[/home/CAE](provider=parsed): Remounting
debug: mount provider parsed: Executing '/bin/mount -o remount /home/CAE'

Any ideas would be appreciated. The rest of the details are below.

=================
manifest section:
=================

node ch208r {
     include cae-host
     package {
         [ "xfsdump", "lvm2", "parted" ]: ensure => installed;
     }
     mount { "/home/CAE":
         atboot  => true,
         device  => "/dev/mapper/md1000-home",
         ensure  => mounted,
         fstype  => "xfs",
         require => [ package["xfsdump"], package["lvm2"]];
     }
     package {
         [ "nfs-kernel-server" ]: ensure => installed;
     }
}

==========
df output:
==========

ch208r:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda1            840369832    979180 796702336   1% /
tmpfs                  1038308         0   1038308   0% /lib/init/rw
udev                     10240        48     10192   1% /dev
tmpfs                  1038308         0   1038308   0% /dev/shm
/dev/mapper/md1000-home
                      9516347392  62499276 9453848116   1% /home/CAE

=============
mount output:
=============

ch208r:~# mount
/dev/sda1 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/mapper/md1000-home on /home/CAE type xfs (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)

===============
fstab contents:
===============

# HEADER: This file was autogenerated at Sun Jul 01 11:31:54 -0500 2007
# HEADER: by puppet.  While it can still be managed manually, it
# HEADER: is definitely not recommended.
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc    /proc   proc    defaults        0       0
/dev/sda1       /       ext3    defaults,errors=remount-ro      0       1
/dev/sda5       none    swap    sw      0       0
/dev/hda        /media/cdrom0   udf,iso9660     user,noauto     0       0

-- 
Mike Renfro  / R&D Engineer, Center for Manufacturing Research,
931 372-3601 / Tennessee Technological University -- renfro at tntech.edu