On 2012-08-10 13:23, Carl Turney wrote:
Hi All,
[...]
Lately, when rsync updates my WinXP partition (by this command)... rsync -Hvxrlt --delete /mnt/tempWindows/ /mnt/backupWindows ... I get the following error messages ...
[...]
*rsync: write failed on “/mnt/backupWindows/pagefile.sys”: No space left on device (28)*
*rsync error: error in file IO (code 11) at receiver.c(302) [receiver=3.0.7]*
*rsync: connection unexpectedly closed (28 bytes received so far) [sender]*
*rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.7]*
[...]
My guess is that the target can only run out of space is if rsync (1) copies an updated file into the free space of the target partition using a temp filename, (2) deletes the original file at the target partition, and (3) renames the newly-copied file to the original name.
Any other explanation for that? Any suggested work-arounds?
I'm thinking about cutting the Win swap file size in half, and seeing if that removes the problem at rsync time. Then limping along with that setup until I rebuild my system (when Ubuntu 12.4.1 comes out in a few weeks), with a larger partition for my "bare bones" WinXP.
Hi Carl, Given this is a swap file, and therefore its contents should only be relevent until a system is rebooted, why bother syncing it at all: rsync --exclude=pagefile.sys Secondly, if you are concerned that you don't have enough space for 2 copies of the file (so that the new copy can be moved into place only after fully transfered), you could try the --inplace option to rsync, which explicitly avoids this behaviour. Finally, I'm surprised that you don't have more issues syncing a Windows partition using the Linux NTFS drivers; I'd assume that this would ignore a while lot of permissions and ACLs which I'd expect to cause problems, or at least insecurities. Interesting to see that it boots at all, but I'd definitely be concerned about permissions issues, though this may not be a problem for your specific use-case. -- Regards, Matthew Cengia