Re: [Sisuite-devel] tmpfs problem?
Jeremy Enos wrote: Thanks Andrea- it may be some time before I get another chance to test this. I had to have the machines up last week so I rebuilt my golden machine from scratch w/o LVM, and all was well. I'll certainly test this at the next opportunity though. Will this patch make the 3.6.3 release? The patch will be surely included in the 3.6.3 release... I don't know if there are other fix before releasing the new version... Regards, -Andrea --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click ___ Sisuite-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
Re: [Sisuite-devel] tmpfs problem?
Thanks Andrea-
it may be some time before I get another chance to test this. I had to
have the machines up last week so I rebuilt my golden machine from
scratch w/o LVM, and all was well. I'll certainly test this at the
next opportunity though. Will this patch make the 3.6.3 release?
thx-
Jeremy
Andrea Righi wrote:
Jeremy,
the attached patch should fix the problem. You can check it applying
the patch directly to the source:
patch -p0 < systemimager-lvm-fix.patch
Let me know if it works.
Thank you for the bug report,
-Andrea
Index: lib/SystemImager/Server.pm
===
--- lib/SystemImager/Server.pm (revision 3399)
+++ lib/SystemImager/Server.pm (working copy)
@@ -1413,8 +1413,9 @@
print $out qq(mkraid --really-force $real_dev || shellout\n)
unless (defined($xml_config->{raid}));
} elsif( $real_dev =~ /^(.*?)(p?\d+)$/ ) {
-unless($dev2disk{$1}) { next; }
-$real_dev = "\${".$dev2disk{$1}."}".$2;
+if ($dev2disk{$1}) {
+$real_dev = "\${".$dev2disk{$1}."}".$2;
+}
}
# swap
Re: [Sisuite-devel] tmpfs problem?
Jeremy,
the attached patch should fix the problem. You can check it applying the
patch directly to the source:
patch -p0 < systemimager-lvm-fix.patch
Let me know if it works.
Thank you for the bug report,
-Andrea
Index: lib/SystemImager/Server.pm
===
--- lib/SystemImager/Server.pm (revision 3399)
+++ lib/SystemImager/Server.pm (working copy)
@@ -1413,8 +1413,9 @@
print $out qq(mkraid --really-force $real_dev || shellout\n)
unless (defined($xml_config->{raid}));
} elsif( $real_dev =~ /^(.*?)(p?\d+)$/ ) {
-unless($dev2disk{$1}) { next; }
-$real_dev = "\${".$dev2disk{$1}."}".$2;
+if ($dev2disk{$1}) {
+$real_dev = "\${".$dev2disk{$1}."}".$2;
+}
}
# swap
RE: [Sisuite-devel] tmpfs problem?
Title: Re: [Sisuite-devel] tmpfs problem? Hey Andrea: Any idea what's wrong here? Think it can be fixed quickly? I'd like to request that we tag 3.6.3 and have it released. If we can include the LVM fixes, all the better. Thanks, Bernard From: [EMAIL PROTECTED] on behalf of Jeremy EnosSent: Thu 05/01/2006 11:42To: [email protected]: Re: [Sisuite-devel] tmpfs problem? That's what I'm guessing. Files attached. JeremyAndrea Righi wrote:> Can you post the autoinstallscript.conf and the master autoinstall> script? IMO there is something wrong during the LVM volumes creation> that could cause a fail when mounting some paths... so the image is> stored in tmpfs, since the right mount point in /a/ is unmounted...>> Regards,> -Andrea>> Jeremy Enos wrote:>>> The tmpfs filling up issue is most definitely related to LVM based>> images. I tried 3.6.2 on the FC3, all else the same other than LVM>> or not... tmpfs filled up when using LVM.>>>> Jeremy
Re: [Sisuite-devel] tmpfs problem?
That's what I'm guessing. Files attached. Jeremy Andrea Righi wrote: Can you post the autoinstallscript.conf and the master autoinstall script? IMO there is something wrong during the LVM volumes creation that could cause a fail when mounting some paths... so the image is stored in tmpfs, since the right mount point in /a/ is unmounted... Regards, -Andrea Jeremy Enos wrote: The tmpfs filling up issue is most definitely related to LVM based images. I tried 3.6.2 on the FC3, all else the same other than LVM or not... tmpfs filled up when using LVM. Jeremy Jeremy Enos wrote: Bad wording... I'm just giving up on LVM at the moment- not SI! ;-) Jeremy Bernard Li wrote: Don't give up Jeremy! I'm sure we can figure it out :-) Cheers, Bernard *From:* [EMAIL PROTECTED] on behalf of Jeremy Enos *Sent:* Wed 04/01/2006 15:06 *To:* Jeremy Enos *Cc:* [email protected] *Subject:* Re: [Sisuite-devel] tmpfs problem? Ignore that... tmpfs is filling up, but not with the image. I'm giving up on this I think. Jeremy Enos wrote: Not sure why, but even when I use the TMPFS_STAGING=no option on the kernel append line when I network boot, it looks like I'm getting the image dumped into tmpfs. Why might this be? Jeremy Jeremy Enos wrote: Also, just read up on tmpfs and saw that it tries to spool the entire 6GB image into that 2GB... no surprise at that failure now that I understand how it works. However... when not using tmpfs to spool (as in the first failure), why would I get an error that tmpfs is full? Jeremy Bernard Li wrote: Just FYI this is probably off stable branch 3.6.x. Cheers, Bernard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Enos Sent: Tuesday, January 03, 2006 16:10 To: [email protected] Subject: [Sisuite-devel] tmpfs problem? Using this version: [EMAIL PROTECTED] root]# rpm -qa |grep systemimager systemimager-client-3.6.3-1 systemimager-common-3.6.3-1 systemimager-i386boot-standard-3.6.3-1 systemimager-server-3.6.3-1 systemimager-i386initrd_template-3.6.3-1 systemimager-flamethrower-3.6.3-1 [EMAIL PROTECTED] root]# It goes through most of the synchronization process: usr/X11R6/lib/X11/doc/Versions usr/X11R6/lib/X11/doc/VideoBoard98 usr/X11R6/lib/X11/doc/Xprint_FAQ.txt usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html rsync: write failed on "/a/usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html": No spac) rsync error: error in file IO (code 11) at receiver.c(291) rsync: connection unexpectedly closed (8560707 bytes received so far) [generato] rsync error: error in rsync protocol data stream (code 12) at io.c(434)Killing off running processes. si_monitortk shows: par4(141.142.237.53):> lvcreate -L2031616K -n LogVol01 VolGroup00 || shellout par4(141.142.237.53):> lvscan > /dev/null; lvchange -a y /dev/VolGroup00/LogVol01 || shellout par4(141.142.237.53):> Load additional filesystem drivers. par4(141.142.237.53):> mke2fs -j /dev/sda1 || shellout par4(141.142.237.53):> tune2fs -L /boot /dev/sda1 par4(141.142.237.53):> mount /dev/sda1 /a/boot -t ext3 -o defaults || shellout par4(141.142.237.53):> mkdir -p /a/proc || shellout par4(141.142.237.53):> mount proc /a/proc -t proc -o defaults || shellout par4(141.142.237.53):> mkdir -p /a/sys || shellout par4(141.142.237.53):> mount sysfs /a/sys -t sysfs -o defaults || shellout par4(141.142.237.53):> Evaluating image size. par4(141.142.237.53):> Report task started. par4(141.142.237.53):> rsync -aHSv --exclude=lost+found/ --exclude=/proc/* --numeric-ids 141.142.237.40::fc3image/ /a/ par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 95% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 96% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 98% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 99% full! par4(141.142.237.53):> Search the FAQ for tmpfs to learn about sizing options. par4(141.142.237.53):> Killing off running processes. par4(141.142.237.53):> write_variables par4(141.142.237.53):> Installation failed!! Stopping report task. par4(141.142.237.53):> Report task stopped. My boot params were: label autoinstall-serial kernel kernel append initrd=initrd.img MONITOR_SERVER=141.142.237.40 console=tty0 console=ttyS0,9600n8 So I changed them to: label autoinstall-serial kernel kernel append initrd=initrd.img tmpfs_size=2G tmpfs_nr_inodes=2000 MONITOR_SERVER=141.142.237.40 console=tty0 console=tt
Re: [Sisuite-devel] tmpfs problem?
Can you post the autoinstallscript.conf and the master autoinstall script? IMO there is something wrong during the LVM volumes creation that could cause a fail when mounting some paths... so the image is stored in tmpfs, since the right mount point in /a/ is unmounted... Regards, -Andrea Jeremy Enos wrote: The tmpfs filling up issue is most definitely related to LVM based images. I tried 3.6.2 on the FC3, all else the same other than LVM or not... tmpfs filled up when using LVM. Jeremy Jeremy Enos wrote: Bad wording... I'm just giving up on LVM at the moment- not SI! ;-) Jeremy Bernard Li wrote: Don't give up Jeremy! I'm sure we can figure it out :-) Cheers, Bernard *From:* [EMAIL PROTECTED] on behalf of Jeremy Enos *Sent:* Wed 04/01/2006 15:06 *To:* Jeremy Enos *Cc:* [email protected] *Subject:* Re: [Sisuite-devel] tmpfs problem? Ignore that... tmpfs is filling up, but not with the image. I'm giving up on this I think. Jeremy Enos wrote: Not sure why, but even when I use the TMPFS_STAGING=no option on the kernel append line when I network boot, it looks like I'm getting the image dumped into tmpfs. Why might this be? Jeremy Jeremy Enos wrote: Also, just read up on tmpfs and saw that it tries to spool the entire 6GB image into that 2GB... no surprise at that failure now that I understand how it works. However... when not using tmpfs to spool (as in the first failure), why would I get an error that tmpfs is full? Jeremy Bernard Li wrote: Just FYI this is probably off stable branch 3.6.x. Cheers, Bernard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Enos Sent: Tuesday, January 03, 2006 16:10 To: [email protected] Subject: [Sisuite-devel] tmpfs problem? Using this version: [EMAIL PROTECTED] root]# rpm -qa |grep systemimager systemimager-client-3.6.3-1 systemimager-common-3.6.3-1 systemimager-i386boot-standard-3.6.3-1 systemimager-server-3.6.3-1 systemimager-i386initrd_template-3.6.3-1 systemimager-flamethrower-3.6.3-1 [EMAIL PROTECTED] root]# It goes through most of the synchronization process: usr/X11R6/lib/X11/doc/Versions usr/X11R6/lib/X11/doc/VideoBoard98 usr/X11R6/lib/X11/doc/Xprint_FAQ.txt usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html rsync: write failed on "/a/usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html": No spac) rsync error: error in file IO (code 11) at receiver.c(291) rsync: connection unexpectedly closed (8560707 bytes received so far) [generato] rsync error: error in rsync protocol data stream (code 12) at io.c(434)Killing off running processes. si_monitortk shows: par4(141.142.237.53):> lvcreate -L2031616K -n LogVol01 VolGroup00 || shellout par4(141.142.237.53):> lvscan > /dev/null; lvchange -a y /dev/VolGroup00/LogVol01 || shellout par4(141.142.237.53):> Load additional filesystem drivers. par4(141.142.237.53):> mke2fs -j /dev/sda1 || shellout par4(141.142.237.53):> tune2fs -L /boot /dev/sda1 par4(141.142.237.53):> mount /dev/sda1 /a/boot -t ext3 -o defaults || shellout par4(141.142.237.53):> mkdir -p /a/proc || shellout par4(141.142.237.53):> mount proc /a/proc -t proc -o defaults || shellout par4(141.142.237.53):> mkdir -p /a/sys || shellout par4(141.142.237.53):> mount sysfs /a/sys -t sysfs -o defaults || shellout par4(141.142.237.53):> Evaluating image size. par4(141.142.237.53):> Report task started. par4(141.142.237.53):> rsync -aHSv --exclude=lost+found/ --exclude=/proc/* --numeric-ids 141.142.237.40::fc3image/ /a/ par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 95% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 96% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 98% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 99% full! par4(141.142.237.53):> Search the FAQ for tmpfs to learn about sizing options. par4(141.142.237.53):> Killing off running processes. par4(141.142.237.53):> write_variables par4(141.142.237.53):> Installation failed!! Stopping report task. par4(141.142.237.53):> Report task stopped. My boot params were: label autoinstall-serial kernel kernel append initrd=initrd.img MONITOR_SERVER=141.142.237.40 console=tty0 console=ttyS0,9600n8 So I changed them to: label autoinstall-serial kernel kernel append initrd=initrd.img tmpfs_size=2G tmpfs_nr_inodes=2000 MONITOR_SERVER=141.142.237.40 console=tty0 console=ttyS0,9600n8 Which started syncing for a very short time until failures plague the output t
Re: [Sisuite-devel] tmpfs problem?
The tmpfs filling up issue is most definitely related to LVM based images. I tried 3.6.2 on the FC3, all else the same other than LVM or not... tmpfs filled up when using LVM. Jeremy Jeremy Enos wrote: Bad wording... I'm just giving up on LVM at the moment- not SI! ;-) Jeremy Bernard Li wrote: Don't give up Jeremy! I'm sure we can figure it out :-) Cheers, Bernard *From:* [EMAIL PROTECTED] on behalf of Jeremy Enos *Sent:* Wed 04/01/2006 15:06 *To:* Jeremy Enos *Cc:* [email protected] *Subject:* Re: [Sisuite-devel] tmpfs problem? Ignore that... tmpfs is filling up, but not with the image. I'm giving up on this I think. Jeremy Enos wrote: Not sure why, but even when I use the TMPFS_STAGING=no option on the kernel append line when I network boot, it looks like I'm getting the image dumped into tmpfs. Why might this be? Jeremy Jeremy Enos wrote: Also, just read up on tmpfs and saw that it tries to spool the entire 6GB image into that 2GB... no surprise at that failure now that I understand how it works. However... when not using tmpfs to spool (as in the first failure), why would I get an error that tmpfs is full? Jeremy Bernard Li wrote: Just FYI this is probably off stable branch 3.6.x. Cheers, Bernard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Enos Sent: Tuesday, January 03, 2006 16:10 To: [email protected] Subject: [Sisuite-devel] tmpfs problem? Using this version: [EMAIL PROTECTED] root]# rpm -qa |grep systemimager systemimager-client-3.6.3-1 systemimager-common-3.6.3-1 systemimager-i386boot-standard-3.6.3-1 systemimager-server-3.6.3-1 systemimager-i386initrd_template-3.6.3-1 systemimager-flamethrower-3.6.3-1 [EMAIL PROTECTED] root]# It goes through most of the synchronization process: usr/X11R6/lib/X11/doc/Versions usr/X11R6/lib/X11/doc/VideoBoard98 usr/X11R6/lib/X11/doc/Xprint_FAQ.txt usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html rsync: write failed on "/a/usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html": No spac) rsync error: error in file IO (code 11) at receiver.c(291) rsync: connection unexpectedly closed (8560707 bytes received so far) [generato] rsync error: error in rsync protocol data stream (code 12) at io.c(434)Killing off running processes. si_monitortk shows: par4(141.142.237.53):> lvcreate -L2031616K -n LogVol01 VolGroup00 || shellout par4(141.142.237.53):> lvscan > /dev/null; lvchange -a y /dev/VolGroup00/LogVol01 || shellout par4(141.142.237.53):> Load additional filesystem drivers. par4(141.142.237.53):> mke2fs -j /dev/sda1 || shellout par4(141.142.237.53):> tune2fs -L /boot /dev/sda1 par4(141.142.237.53):> mount /dev/sda1 /a/boot -t ext3 -o defaults || shellout par4(141.142.237.53):> mkdir -p /a/proc || shellout par4(141.142.237.53):> mount proc /a/proc -t proc -o defaults || shellout par4(141.142.237.53):> mkdir -p /a/sys || shellout par4(141.142.237.53):> mount sysfs /a/sys -t sysfs -o defaults || shellout par4(141.142.237.53):> Evaluating image size. par4(141.142.237.53):> Report task started. par4(141.142.237.53):> rsync -aHSv --exclude=lost+found/ --exclude=/proc/* --numeric-ids 141.142.237.40::fc3image/ /a/ par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 95% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 96% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 98% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 99% full! par4(141.142.237.53):> Search the FAQ for tmpfs to learn about sizing options. par4(141.142.237.53):> Killing off running processes. par4(141.142.237.53):> write_variables par4(141.142.237.53):> Installation failed!! Stopping report task. par4(141.142.237.53):> Report task stopped. My boot params were: label autoinstall-serial kernel kernel append initrd=initrd.img MONITOR_SERVER=141.142.237.40 console=tty0 console=ttyS0,9600n8 So I changed them to: label autoinstall-serial kernel kernel append initrd=initrd.img tmpfs_size=2G tmpfs_nr_inodes=2000 MONITOR_SERVER=141.142.237.40 console=tty0 console=ttyS0,9600n8 Which started syncing for a very short time until failures plague the output thereafter: etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ show_desktop_butt/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ systray/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ window_list/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/
Re: [Sisuite-devel] tmpfs problem?
Bad wording... I'm just giving up on LVM at the moment- not SI! ;-) Jeremy Bernard Li wrote: Don't give up Jeremy! I'm sure we can figure it out :-) Cheers, Bernard *From:* [EMAIL PROTECTED] on behalf of Jeremy Enos *Sent:* Wed 04/01/2006 15:06 *To:* Jeremy Enos *Cc:* [email protected] *Subject:* Re: [Sisuite-devel] tmpfs problem? Ignore that... tmpfs is filling up, but not with the image. I'm giving up on this I think. Jeremy Enos wrote: Not sure why, but even when I use the TMPFS_STAGING=no option on the kernel append line when I network boot, it looks like I'm getting the image dumped into tmpfs. Why might this be? Jeremy Jeremy Enos wrote: Also, just read up on tmpfs and saw that it tries to spool the entire 6GB image into that 2GB... no surprise at that failure now that I understand how it works. However... when not using tmpfs to spool (as in the first failure), why would I get an error that tmpfs is full? Jeremy Bernard Li wrote: Just FYI this is probably off stable branch 3.6.x. Cheers, Bernard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Enos Sent: Tuesday, January 03, 2006 16:10 To: [email protected] Subject: [Sisuite-devel] tmpfs problem? Using this version: [EMAIL PROTECTED] root]# rpm -qa |grep systemimager systemimager-client-3.6.3-1 systemimager-common-3.6.3-1 systemimager-i386boot-standard-3.6.3-1 systemimager-server-3.6.3-1 systemimager-i386initrd_template-3.6.3-1 systemimager-flamethrower-3.6.3-1 [EMAIL PROTECTED] root]# It goes through most of the synchronization process: usr/X11R6/lib/X11/doc/Versions usr/X11R6/lib/X11/doc/VideoBoard98 usr/X11R6/lib/X11/doc/Xprint_FAQ.txt usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html rsync: write failed on "/a/usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html": No spac) rsync error: error in file IO (code 11) at receiver.c(291) rsync: connection unexpectedly closed (8560707 bytes received so far) [generato] rsync error: error in rsync protocol data stream (code 12) at io.c(434) Killing off running processes. si_monitortk shows: par4(141.142.237.53):> lvcreate -L2031616K -n LogVol01 VolGroup00 || shellout par4(141.142.237.53):> lvscan > /dev/null; lvchange -a y /dev/VolGroup00/LogVol01 || shellout par4(141.142.237.53):> Load additional filesystem drivers. par4(141.142.237.53):> mke2fs -j /dev/sda1 || shellout par4(141.142.237.53):> tune2fs -L /boot /dev/sda1 par4(141.142.237.53):> mount /dev/sda1 /a/boot -t ext3 -o defaults || shellout par4(141.142.237.53):> mkdir -p /a/proc || shellout par4(141.142.237.53):> mount proc /a/proc -t proc -o defaults || shellout par4(141.142.237.53):> mkdir -p /a/sys || shellout par4(141.142.237.53):> mount sysfs /a/sys -t sysfs -o defaults || shellout par4(141.142.237.53):> Evaluating image size. par4(141.142.237.53):> Report task started. par4(141.142.237.53):> rsync -aHSv --exclude=lost+found/ --exclude=/proc/* --numeric-ids 141.142.237.40::fc3image/ /a/ par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 95% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 96% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 98% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 99% full! par4(141.142.237.53):> Search the FAQ for tmpfs to learn about sizing options. par4(141.142.237.53):> Killing off running processes. par4(141.142.237.53):> write_variables par4(141.142.237.53):> Installation failed!! Stopping report task. par4(141.142.237.53):> Report task stopped. My boot params were: label autoinstall-serial kernel kernel append initrd=initrd.img MONITOR_SERVER=141.142.237.40 console=tty0 console=ttyS0,9600n8 So I changed them to: label autoinstall-serial kernel kernel append initrd=initrd.img tmpfs_size=2G tmpfs_nr_inodes=2000 MONITOR_SERVER=141.142.237.40 console=tty0 console=ttyS0,9600n8 Which started syncing for a very short time until failures plague the output thereafter: etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ show_desktop_butt/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ systray/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ window_list/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ workspace_switche/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ workspace_switche/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/general/ etc/gconf/gc
RE: [Sisuite-devel] tmpfs problem?
Don't give up Jeremy! I'm sure we can figure it out :-) Cheers, Bernard From: [EMAIL PROTECTED] on behalf of Jeremy EnosSent: Wed 04/01/2006 15:06To: Jeremy EnosCc: [email protected]: Re: [Sisuite-devel] tmpfs problem? Ignore that... tmpfs is filling up, but not with the image. I'm giving up on this I think.Jeremy Enos wrote: Not sure why, but even when I use the TMPFS_STAGING=no option on the kernel append line when I network boot, it looks like I'm getting the image dumped into tmpfs. Why might this be? JeremyJeremy Enos wrote: Also, just read up on tmpfs and saw that it tries to spool the entire 6GB image into that 2GB... no surprise at that failure now that I understand how it works.However... when not using tmpfs to spool (as in the first failure), why would I get an error that tmpfs is full? JeremyBernard Li wrote: Just FYI this is probably off stable branch 3.6.x. Cheers, Bernard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jeremy Enos Sent: Tuesday, January 03, 2006 16:10 To: [email protected] Subject: [Sisuite-devel] tmpfs problem? Using this version: [EMAIL PROTECTED] root]# rpm -qa |grep systemimager systemimager-client-3.6.3-1 systemimager-common-3.6.3-1 systemimager-i386boot-standard-3.6.3-1 systemimager-server-3.6.3-1 systemimager-i386initrd_template-3.6.3-1 systemimager-flamethrower-3.6.3-1 [EMAIL PROTECTED] root]# It goes through most of the synchronization process: usr/X11R6/lib/X11/doc/Versions usr/X11R6/lib/X11/doc/VideoBoard98 usr/X11R6/lib/X11/doc/Xprint_FAQ.txt usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html rsync: write failed on "/a/usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html": No spac) rsync error: error in file IO (code 11) at receiver.c(291) rsync: connection unexpectedly closed (8560707 bytes received so far) [generato] rsync error: error in rsync protocol data stream (code 12) at io.c(434) Killing off running processes. si_monitortk shows: par4(141.142.237.53):> lvcreate -L2031616K -n LogVol01 VolGroup00 || shellout par4(141.142.237.53):> lvscan > /dev/null; lvchange -a y /dev/VolGroup00/LogVol01 || shellout par4(141.142.237.53):> Load additional filesystem drivers. par4(141.142.237.53):> mke2fs -j /dev/sda1 || shellout par4(141.142.237.53):> tune2fs -L /boot /dev/sda1 par4(141.142.237.53):> mount /dev/sda1 /a/boot -t ext3 -o defaults || shellout par4(141.142.237.53):> mkdir -p /a/proc || shellout par4(141.142.237.53):> mount proc /a/proc -t proc -o defaults || shellout par4(141.142.237.53):> mkdir -p /a/sys || shellout par4(141.142.237.53):> mount sysfs /a/sys -t sysfs -o defaults || shellout par4(141.142.237.53):> Evaluating image size. par4(141.142.237.53):> Report task started. par4(141.142.237.53):> rsync -aHSv --exclude=lost+found/ --exclude=/proc/* --numeric-ids 141.142.237.40::fc3image/ /a/ par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 95% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 96% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 98% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 99% full! par4(141.142.237.53):> Search the FAQ for tmpfs to learn about sizing options. par4(141.142.237.53):> Killing off running processes. par4(141.142.237.53):> write_variables par4(141.142.237.53):> Installation failed!! Stopping report task. par4(141.142.237.53):> Report task stopped. My boot params were: label autoinstall-serial kernel kernel append initrd=initrd.img MONITOR_SERVER=141.142.237.40 console=tty0 console=ttyS0,9600n8 So I changed them to: label autoinstall-serial kernel kernel append initrd=initrd.img tmpfs_size=2G tmpfs_nr_inodes=2000 MONITOR_SERVER=141.142.237.40 console=tty0 console=ttyS0,9600n8 Which started syncing for a very short time until failures plague the output thereafter: etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ show_desktop_butt/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ systray/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ window_list/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ workspace_switche/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ workspace_switche/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/general/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/ email_launcher/ rsync: re
Re: [Sisuite-devel] tmpfs problem?
Ignore that... tmpfs is filling up, but not with the image. I'm giving up on this I think. Jeremy Enos wrote: Not sure why, but even when I use the TMPFS_STAGING=no option on the kernel append line when I network boot, it looks like I'm getting the image dumped into tmpfs. Why might this be? Jeremy Jeremy Enos wrote: Also, just read up on tmpfs and saw that it tries to spool the entire 6GB image into that 2GB... no surprise at that failure now that I understand how it works. However... when not using tmpfs to spool (as in the first failure), why would I get an error that tmpfs is full? Jeremy Bernard Li wrote: Just FYI this is probably off stable branch 3.6.x. Cheers, Bernard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jeremy Enos Sent: Tuesday, January 03, 2006 16:10 To: [email protected] Subject: [Sisuite-devel] tmpfs problem? Using this version: [EMAIL PROTECTED] root]# rpm -qa |grep systemimager systemimager-client-3.6.3-1 systemimager-common-3.6.3-1 systemimager-i386boot-standard-3.6.3-1 systemimager-server-3.6.3-1 systemimager-i386initrd_template-3.6.3-1 systemimager-flamethrower-3.6.3-1 [EMAIL PROTECTED] root]# It goes through most of the synchronization process: usr/X11R6/lib/X11/doc/Versions usr/X11R6/lib/X11/doc/VideoBoard98 usr/X11R6/lib/X11/doc/Xprint_FAQ.txt usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html rsync: write failed on "/a/usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html": No spac) rsync error: error in file IO (code 11) at receiver.c(291) rsync: connection unexpectedly closed (8560707 bytes received so far) [generato] rsync error: error in rsync protocol data stream (code 12) at io.c(434) Killing off running processes. si_monitortk shows: par4(141.142.237.53):> lvcreate -L2031616K -n LogVol01 VolGroup00 || shellout par4(141.142.237.53):> lvscan > /dev/null; lvchange -a y /dev/VolGroup00/LogVol01 || shellout par4(141.142.237.53):> Load additional filesystem drivers. par4(141.142.237.53):> mke2fs -j /dev/sda1 || shellout par4(141.142.237.53):> tune2fs -L /boot /dev/sda1 par4(141.142.237.53):> mount /dev/sda1 /a/boot -t ext3 -o defaults || shellout par4(141.142.237.53):> mkdir -p /a/proc || shellout par4(141.142.237.53):> mount proc /a/proc -t proc -o defaults || shellout par4(141.142.237.53):> mkdir -p /a/sys || shellout par4(141.142.237.53):> mount sysfs /a/sys -t sysfs -o defaults || shellout par4(141.142.237.53):> Evaluating image size. par4(141.142.237.53):> Report task started. par4(141.142.237.53):> rsync -aHSv --exclude=lost+found/ --exclude=/proc/* --numeric-ids 141.142.237.40::fc3image/ /a/ par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 95% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 96% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 98% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 99% full! par4(141.142.237.53):> Search the FAQ for tmpfs to learn about sizing options. par4(141.142.237.53):> Killing off running processes. par4(141.142.237.53):> write_variables par4(141.142.237.53):> Installation failed!! Stopping report task. par4(141.142.237.53):> Report task stopped. My boot params were: label autoinstall-serial kernel kernel append initrd=initrd.img MONITOR_SERVER=141.142.237.40 console=tty0 console=ttyS0,9600n8 So I changed them to: label autoinstall-serial kernel kernel append initrd=initrd.img tmpfs_size=2G tmpfs_nr_inodes=2000 MONITOR_SERVER=141.142.237.40 console=tty0 console=ttyS0,9600n8 Which started syncing for a very short time until failures plague the output thereafter: etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ show_desktop_butt/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ systray/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ window_list/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ workspace_switche/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ workspace_switche/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/general/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/ email_launcher/ rsync: recv_generator: mkdir "/a/etc/gconf/gconf.xml.defaults/apps/panel/defaul) rsync: stat "/a/etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/m) rsync: recv_generator: mkdir "/a/etc/gconf/gconf.xml.defaults/apps/panel/defaul) rsync: stat "/a/etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/p) rsync: recv_generator:
Re: [Sisuite-devel] tmpfs problem?
Not sure why, but even when I use the TMPFS_STAGING=no option on the kernel append line when I network boot, it looks like I'm getting the image dumped into tmpfs. Why might this be? Jeremy Jeremy Enos wrote: Also, just read up on tmpfs and saw that it tries to spool the entire 6GB image into that 2GB... no surprise at that failure now that I understand how it works. However... when not using tmpfs to spool (as in the first failure), why would I get an error that tmpfs is full? Jeremy Bernard Li wrote: Just FYI this is probably off stable branch 3.6.x. Cheers, Bernard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jeremy Enos Sent: Tuesday, January 03, 2006 16:10 To: [email protected] Subject: [Sisuite-devel] tmpfs problem? Using this version: [EMAIL PROTECTED] root]# rpm -qa |grep systemimager systemimager-client-3.6.3-1 systemimager-common-3.6.3-1 systemimager-i386boot-standard-3.6.3-1 systemimager-server-3.6.3-1 systemimager-i386initrd_template-3.6.3-1 systemimager-flamethrower-3.6.3-1 [EMAIL PROTECTED] root]# It goes through most of the synchronization process: usr/X11R6/lib/X11/doc/Versions usr/X11R6/lib/X11/doc/VideoBoard98 usr/X11R6/lib/X11/doc/Xprint_FAQ.txt usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html rsync: write failed on "/a/usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html": No spac) rsync error: error in file IO (code 11) at receiver.c(291) rsync: connection unexpectedly closed (8560707 bytes received so far) [generato] rsync error: error in rsync protocol data stream (code 12) at io.c(434) Killing off running processes. si_monitortk shows: par4(141.142.237.53):> lvcreate -L2031616K -n LogVol01 VolGroup00 || shellout par4(141.142.237.53):> lvscan > /dev/null; lvchange -a y /dev/VolGroup00/LogVol01 || shellout par4(141.142.237.53):> Load additional filesystem drivers. par4(141.142.237.53):> mke2fs -j /dev/sda1 || shellout par4(141.142.237.53):> tune2fs -L /boot /dev/sda1 par4(141.142.237.53):> mount /dev/sda1 /a/boot -t ext3 -o defaults || shellout par4(141.142.237.53):> mkdir -p /a/proc || shellout par4(141.142.237.53):> mount proc /a/proc -t proc -o defaults || shellout par4(141.142.237.53):> mkdir -p /a/sys || shellout par4(141.142.237.53):> mount sysfs /a/sys -t sysfs -o defaults || shellout par4(141.142.237.53):> Evaluating image size. par4(141.142.237.53):> Report task started. par4(141.142.237.53):> rsync -aHSv --exclude=lost+found/ --exclude=/proc/* --numeric-ids 141.142.237.40::fc3image/ /a/ par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 95% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 96% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 98% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 99% full! par4(141.142.237.53):> Search the FAQ for tmpfs to learn about sizing options. par4(141.142.237.53):> Killing off running processes. par4(141.142.237.53):> write_variables par4(141.142.237.53):> Installation failed!! Stopping report task. par4(141.142.237.53):> Report task stopped. My boot params were: label autoinstall-serial kernel kernel append initrd=initrd.img MONITOR_SERVER=141.142.237.40 console=tty0 console=ttyS0,9600n8 So I changed them to: label autoinstall-serial kernel kernel append initrd=initrd.img tmpfs_size=2G tmpfs_nr_inodes=2000 MONITOR_SERVER=141.142.237.40 console=tty0 console=ttyS0,9600n8 Which started syncing for a very short time until failures plague the output thereafter: etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ show_desktop_butt/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ systray/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ window_list/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ workspace_switche/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ workspace_switche/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/general/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/ email_launcher/ rsync: recv_generator: mkdir "/a/etc/gconf/gconf.xml.defaults/apps/panel/defaul) rsync: stat "/a/etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/m) rsync: recv_generator: mkdir "/a/etc/gconf/gconf.xml.defaults/apps/panel/defaul) rsync: stat "/a/etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/p) rsync: recv_generator: mkdir "/a/etc/gconf/gconf.xml.defaults/apps/panel/defaul) rsync: stat
Re: [Sisuite-devel] tmpfs problem?
Also, just read up on tmpfs and saw that it tries to spool the entire 6GB image into that 2GB... no surprise at that failure now that I understand how it works. However... when not using tmpfs to spool (as in the first failure), why would I get an error that tmpfs is full? Jeremy Bernard Li wrote: Just FYI this is probably off stable branch 3.6.x. Cheers, Bernard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jeremy Enos Sent: Tuesday, January 03, 2006 16:10 To: [email protected] Subject: [Sisuite-devel] tmpfs problem? Using this version: [EMAIL PROTECTED] root]# rpm -qa |grep systemimager systemimager-client-3.6.3-1 systemimager-common-3.6.3-1 systemimager-i386boot-standard-3.6.3-1 systemimager-server-3.6.3-1 systemimager-i386initrd_template-3.6.3-1 systemimager-flamethrower-3.6.3-1 [EMAIL PROTECTED] root]# It goes through most of the synchronization process: usr/X11R6/lib/X11/doc/Versions usr/X11R6/lib/X11/doc/VideoBoard98 usr/X11R6/lib/X11/doc/Xprint_FAQ.txt usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html rsync: write failed on "/a/usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html": No spac) rsync error: error in file IO (code 11) at receiver.c(291) rsync: connection unexpectedly closed (8560707 bytes received so far) [generato] rsync error: error in rsync protocol data stream (code 12) at io.c(434) Killing off running processes. si_monitortk shows: par4(141.142.237.53):> lvcreate -L2031616K -n LogVol01 VolGroup00 || shellout par4(141.142.237.53):> lvscan > /dev/null; lvchange -a y /dev/VolGroup00/LogVol01 || shellout par4(141.142.237.53):> Load additional filesystem drivers. par4(141.142.237.53):> mke2fs -j /dev/sda1 || shellout par4(141.142.237.53):> tune2fs -L /boot /dev/sda1 par4(141.142.237.53):> mount /dev/sda1 /a/boot -t ext3 -o defaults || shellout par4(141.142.237.53):> mkdir -p /a/proc || shellout par4(141.142.237.53):> mount proc /a/proc -t proc -o defaults || shellout par4(141.142.237.53):> mkdir -p /a/sys || shellout par4(141.142.237.53):> mount sysfs /a/sys -t sysfs -o defaults || shellout par4(141.142.237.53):> Evaluating image size. par4(141.142.237.53):> Report task started. par4(141.142.237.53):> rsync -aHSv --exclude=lost+found/ --exclude=/proc/* --numeric-ids 141.142.237.40::fc3image/ /a/ par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 95% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 96% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 98% full! par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 99% full! par4(141.142.237.53):> Search the FAQ for tmpfs to learn about sizing options. par4(141.142.237.53):> Killing off running processes. par4(141.142.237.53):> write_variables par4(141.142.237.53):> Installation failed!! Stopping report task. par4(141.142.237.53):> Report task stopped. My boot params were: label autoinstall-serial kernel kernel append initrd=initrd.img MONITOR_SERVER=141.142.237.40 console=tty0 console=ttyS0,9600n8 So I changed them to: label autoinstall-serial kernel kernel append initrd=initrd.img tmpfs_size=2G tmpfs_nr_inodes=2000 MONITOR_SERVER=141.142.237.40 console=tty0 console=ttyS0,9600n8 Which started syncing for a very short time until failures plague the output thereafter: etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ show_desktop_butt/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ systray/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ window_list/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ workspace_switche/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ workspace_switche/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/general/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/ etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/ email_launcher/ rsync: recv_generator: mkdir "/a/etc/gconf/gconf.xml.defaults/apps/panel/defaul) rsync: stat "/a/etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/m) rsync: recv_generator: mkdir "/a/etc/gconf/gconf.xml.defaults/apps/panel/defaul) rsync: stat "/a/etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/p) rsync: recv_generator: mkdir "/a/etc/gconf/gconf.xml.defaults/apps/panel/defaul) rsync: stat "/a/etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/s) rsync: recv_generator: mkdir "/a/etc/gconf/gconf.xml.defaults/apps/panel/defaul) rsync: stat "/a/etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/w) rsync: recv_generator: mkdir
RE: [Sisuite-devel] tmpfs problem?
Just FYI this is probably off stable branch 3.6.x. Cheers, Bernard > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Jeremy Enos > Sent: Tuesday, January 03, 2006 16:10 > To: [email protected] > Subject: [Sisuite-devel] tmpfs problem? > > Using this version: > [EMAIL PROTECTED] root]# rpm -qa |grep systemimager > systemimager-client-3.6.3-1 > systemimager-common-3.6.3-1 > systemimager-i386boot-standard-3.6.3-1 > systemimager-server-3.6.3-1 > systemimager-i386initrd_template-3.6.3-1 > systemimager-flamethrower-3.6.3-1 > [EMAIL PROTECTED] root]# > > It goes through most of the synchronization process: > > usr/X11R6/lib/X11/doc/Versions > > > usr/X11R6/lib/X11/doc/VideoBoard98 > > > usr/X11R6/lib/X11/doc/Xprint_FAQ.txt > > > usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html > > > rsync: write failed on > "/a/usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html": > No spac) > rsync error: error in file IO (code 11) at > receiver.c(291) > rsync: connection unexpectedly closed (8560707 bytes received so far) > [generato] > rsync error: error in rsync protocol data stream (code 12) at > io.c(434) > Killing off running > processes. > > si_monitortk shows: > > par4(141.142.237.53):> lvcreate -L2031616K -n LogVol01 VolGroup00 || > shellout > par4(141.142.237.53):> lvscan > /dev/null; lvchange -a y > /dev/VolGroup00/LogVol01 || shellout > par4(141.142.237.53):> Load additional filesystem drivers. > par4(141.142.237.53):> mke2fs -j /dev/sda1 || shellout > par4(141.142.237.53):> tune2fs -L /boot /dev/sda1 > par4(141.142.237.53):> mount /dev/sda1 /a/boot -t ext3 -o defaults || > shellout > par4(141.142.237.53):> mkdir -p /a/proc || shellout > par4(141.142.237.53):> mount proc /a/proc -t proc -o defaults > || shellout > par4(141.142.237.53):> mkdir -p /a/sys || shellout > par4(141.142.237.53):> mount sysfs /a/sys -t sysfs -o > defaults || shellout > par4(141.142.237.53):> Evaluating image size. > par4(141.142.237.53):> Report task started. > par4(141.142.237.53):> rsync -aHSv --exclude=lost+found/ > --exclude=/proc/* --numeric-ids 141.142.237.40::fc3image/ /a/ > par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 95% full! > par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 96% full! > par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 98% full! > par4(141.142.237.53):> WARNING: Your tmpfs filesystem is 99% full! > par4(141.142.237.53):> Search the FAQ for tmpfs to > learn about > sizing options. > par4(141.142.237.53):> Killing off running processes. > par4(141.142.237.53):> write_variables > par4(141.142.237.53):> Installation failed!! Stopping report task. > par4(141.142.237.53):> Report task stopped. > > My boot params were: > label autoinstall-serial > kernel kernel > append initrd=initrd.img MONITOR_SERVER=141.142.237.40 console=tty0 > console=ttyS0,9600n8 > > So I changed them to: > label autoinstall-serial > kernel kernel > append initrd=initrd.img tmpfs_size=2G tmpfs_nr_inodes=2000 > MONITOR_SERVER=141.142.237.40 console=tty0 console=ttyS0,9600n8 > > Which started syncing for a very short time until failures plague the > output thereafter: > > etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ > show_desktop_butt/ > etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ > systray/ > > etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ > window_list/ > > etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ > workspace_switche/ > etc/gconf/gconf.xml.defaults/apps/panel/default_setup/applets/ > workspace_switche/ > etc/gconf/gconf.xml.defaults/apps/panel/default_setup/general/ > > > etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/ > > > etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/ > email_launcher/ > > rsync: recv_generator: mkdir > "/a/etc/gconf/gconf.xml.defaults/apps/panel/defaul) > rsync: stat > "/a/etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/m) > rsync: recv_generator: mkdir > "/a/etc/gconf/gconf.xml.defaults/apps/panel/defaul) > rsync: stat > "/a/etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/p) > rsync: recv_generator: mkdir > "/a/etc/gconf/gconf.xml.defaults/apps/panel/defaul) > rsync: stat > "/a/etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/s) > rsync: recv_generator: mkdir > "/a/etc/gconf/gconf.xml.defaults/apps/panel/defaul) > rsync: stat > "/a/etc/gconf/gconf.xml.defaults/apps/panel/default_setup/objects/w) > rsync: recv_generator: mkdir > "/a/etc/gconf/gconf.xml.defaults/apps/panel/defaul) > rsync: stat >
