Bug 158260

Summary: rsync hangs when target disk is full
Product: [Fedora] Fedora Reporter: Jamie Zawinski <jwz>
Component: rsyncAssignee: Simo Sorce <ssorce>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: mattdm
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-02-16 15:01:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jamie Zawinski 2005-05-20 01:12:00 UTC
When running rsync through ssh to another host, it silently hangs if the target
disk fills up.

rsync-2.6.3-1 and
Linux 2.6.10-1.770_FC3 #1 Thu Feb 24 14:00:06 EST 2005 i686 athlon i386
on both machines.

Reproducible 90% of the time.  E.g., if the disk fills up while in the midst of
sending a large file, rsync hangs silently.  But, if the disk is already full
before sending a file (I think?), then you might get an error message like

    rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown"
      [sender]: Broken pipe (32)
    rsync: write failed on "foo": No space left on device (28)
    rsync error: error in file IO (code 11) at receiver.c(305)
    rsync: connection unexpectedly closed (2256357 bytes received so far)
      [generator]
    rsync error: error in rsync protocol data stream (code 12) at io.c(359)
    unexpected tag 109
    rsync error: error in rsync protocol data stream (code 12) at io.c(689)

But not usually.

My arguments, for the record:

    --rsh ssh --recursive --links --perms --times --owner --group --sparse
    --hard-links --delete --force --verbose

Comment 1 Matthew Miller 2006-07-10 22:50:35 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!


Comment 2 Simo Sorce 2007-02-16 15:01:35 UTC
No activity, close it, reopen if present in newer releases.