DO NOT REPLY [Bug 5795] error in rsync protocol data stream (code 12) at io.c(632) [sender=3.0.4]

samba-bugs at samba-bugs at
Sat Sep 27 23:23:52 GMT 2008

------- Comment #1 from Dave at  2008-09-27 18:23 CST -------
It turns out there was clearly not enough space on the destination. The copy
was going to take 20GB, and after the crash there was still 1GB on the
destination, so I thought this was probably a protocol bug rather than a
problem with running out of space.

Perhaps what this is is a situation where the remote end should have sent back
an indication that it was out of space and should have shut down gracefully.

But there is another problem here: the two ends should start out by negotating
whether there is enough space for the copy. In a better world, the destination
OS would give the rsync process the ability to atomically grab disk resources
up front to be used for the files and folders it creates, and if that fails,
the remote rsync would tell the UI rsync no dice. Or how about this: writing
the destination files could be transaction in the OS file system! Nah.

Configure bugmail:
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

More information about the rsync mailing list