Hey all, I'm trying to clone some images here and am running up against what appear to be some rsync errors.
On my golden client, I did: sudo si_prepareclient --server 192.168.7.10 On my image server, I did: si_getimage -golden-client 192.168.2.165 -image shuttleFieldBackupPC -ip-assignment replicant si_mkautoinstallcd --out-file /var/lib/systemimager/iso/shuttleFieldBackupPC.iso --kernel /usr/share/systemimager/boot/x86_64/shuttleFieldBackupPC/kernel --initrd /usr/share/systemimager/boot/x86_64/shuttleFieldBackupPC/initrd.img --append "IMAGESERVER=192.168.7.10 IMAGENAME=shuttleFieldBackupPC tmpfs_size=5000M" All of that works just fine and I have a 2.5GB image sitting on my image server. When I boot off of that CD, however, the install goes fine until it gets to this point: rsync -aHS --exclude=lost+found/ --exclude=/proc/* --numeric-ids 192.168.7.10::shuttleFieldBackupPC/ /a/ That runs for about 4 minutes or so and I can confirm that lots of data is travelling from my image server onto my clone. However, after about 4 minutes, I start seeing tons of errors similar to on the clone's console: rsync: mkstemp "/a/usr/share/man/man3/.stapprobes.tcp" failed: No space left on device (28) Those errors are all the same except the filename is always different. The console then hangs again for about 10 more minutes (I'm assuming here that this is just the rsync timeout) and dies with the "your autoinstall has failed" error. Any ideas what is running out of space here? When I do a "df" at the busybox prompt, I see: Rootfs 45% / Tmpfs 45% / Devpts 0% /dev/pts Tmpfs 45% /dfev/.static/dev Udev 0% /dev /dev/md0 12% /a/boot If I do a "du -s" at the root directory, I see that I'm currently storing 2.3GB of data. Any ideas? Best, -Jeff ------------------------------------------------------------------------------ _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
