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@tntech.edu
On Jul 1, 2007, at 12:06 PM, Mike Renfro wrote:> 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.This seems likely to the be problem. I just looked at the source and I don''t make any allowances for those multi-line mount statements. Can you file this? I''m hoping to get a small bugfix release out soon with the (surprisingly) few bugs that made it into 0.23.0. -- True Terror is to wake up one morning and discover that your high school class is running the country. -- Kurt Vonnegut --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
i tried to implement this simple fix for my current platform, but i still am not getting a fstab written out on my changes. my debugging shows that its pulling the right df output however: what might i be missing ? # diff provider/mount.rb provider/mount_orig.rb 41c41 < case Facter["kernel"].value --- > case Facter["operatingsystem"].value 43,44c43 < when "SunOS": df << "-k" < when "Linux": df << "-P" --- > when "Solaris": df << "-k" 46d44 < 49,50d46 < Puppet.debug "Raw: %s" % line < Puppet.debug "Parsed: %s" % line.split(/\s+/)[-1] heres the debug output showing that the parse went ok, but like i said still no write or change to the mounted state: notice: Starting configuration run debug: Prefetching parsed resources for mount debug: Prefetching parsed resources for host debug: Mount[usr](provider=parsed): Executing ''/bin/df -P'' debug: Raw: Filesystem 1024-blocks Used Available Capacity Mounted on debug: Parsed: on debug: Raw: /dev/sda2 1968528 250380 1618148 14% / debug: Parsed: / debug: Raw: /dev/sda1 243999 13621 217781 6% /boot debug: Parsed: /boot debug: Raw: tmpfs 513480 0 513480 0% /dev/shm debug: Parsed: /dev/shm debug: Raw: /dev/mapper/vg01-opt 4128448 359156 3559580 10% /opt debug: Parsed: /opt debug: Raw: /dev/mapper/vg01-tmp 4128448 131280 3787456 4% /tmp debug: Parsed: /tmp debug: Raw: /dev/mapper/vg01-usr 4128448 626292 3292444 16% /usr debug: Parsed: /usr debug: //sfptrk01/centos_mounts/Mount[usr]: Changing options,pass,dump debug: //sfptrk01/centos_mounts/Mount[usr]: 3 change(s) notice: //sfptrk01/centos_mounts/Mount[usr]/options: defined ''options'' as ''nodev,noatime,nosuid'' notice: //sfptrk01/centos_mounts/Mount[usr]/pass: defined ''pass'' as ''0'' notice: //sfptrk01/centos_mounts/Mount[usr]/dump: defined ''dump'' as ''0'' debug: Flushing mount provider target /etc/fstab notice: //sfptrk01/centos_mounts/Mount[usr]: Refreshing self info: Mount[usr](provider=parsed): Remounting debug: mount provider parsed: Executing ''/bin/mount -o remount /usr'' debug: Finishing transaction 23456259884500 with 3 changes debug: Storing state debug: Stored state in 0.07 seconds notice: Finished configuration run in 0.23 seconds On Jul 2, 2007, at 12:05 PM, Luke Kanies wrote:> On Jul 1, 2007, at 12:06 PM, Mike Renfro wrote: > > > 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. > > This seems likely to the be problem. I just looked at the source and > I don''t make any allowances for those multi-line mount statements. > > Can you file this? I''m hoping to get a small bugfix release out soon > with the (surprisingly) few bugs that made it into 0.23.0. > > -- > True Terror is to wake up one morning and discover that your high > school class is running the country. -- Kurt Vonnegut > > --------------------------------------------------------------------- > Luke Kanies | http://reductivelabs.com | http://madstop.com > > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users >
On Jul 7, 2007, at 5:13 AM, Jesse Nelson wrote:> i tried to implement this simple fix for my current platform, but i > still am not getting a fstab written out on my changes. my debugging > shows that its pulling the right df output however:Can you attach this as a patch to #702? I''ll hopefully be looking at this this week, although I''ve got a bunch of client work to do, too, so I''m concerned about getting 0.23.1 out very quickly. -- I have an answering machine in my car. It says, "I''m home now. But leave a message and I''ll call when I''m out. -- Stephen Wright --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
On 7/8/2007 1:24 PM, Luke Kanies wrote:> On Jul 7, 2007, at 5:13 AM, Jesse Nelson wrote: > >> i tried to implement this simple fix for my current platform, but i >> still am not getting a fstab written out on my changes. my debugging >> shows that its pulling the right df output however: > > Can you attach this as a patch to #702? I''ll hopefully be looking at > this this week, although I''ve got a bunch of client work to do, too, > so I''m concerned about getting 0.23.1 out very quickly.And I may have been completely wrong about my assumptions on why my RAID wasn''t mounting. I''ll hopefully know for certain by the end of the day. -- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University -- renfro@tntech.edu
On 7/9/2007 1:18 PM, Mike Renfro wrote:> On 7/8/2007 1:24 PM, Luke Kanies wrote: >> On Jul 7, 2007, at 5:13 AM, Jesse Nelson wrote: >> >>> i tried to implement this simple fix for my current platform, but i >>> still am not getting a fstab written out on my changes. my debugging >>> shows that its pulling the right df output however: >> Can you attach this as a patch to #702? I''ll hopefully be looking at >> this this week, although I''ve got a bunch of client work to do, too, >> so I''m concerned about getting 0.23.1 out very quickly. > > And I may have been completely wrong about my assumptions on why my RAID > wasn''t mounting. I''ll hopefully know for certain by the end of the day.Long-overdue followup. Using: mount { "/home": atboot => true, device => "/dev/md1000/home", ensure => mounted, fstype => "xfs", options => "defaults", dump => "0", pass => "1", require => [ Package["xfsdump"], Package["lvm2"] ]; } with the atboot, device, fstype, options, dump, and pass options made it write the fstab entry. I had mistakenly assumed some defaults were in place. -- Mike Renfro / R&D Engineer, Center for Manufacturing Research, 931 372-3601 / Tennessee Technological University -- renfro@tntech.edu