Bug 158260 - rsync hangs when target disk is full
rsync hangs when target disk is full
Product: Fedora
Classification: Fedora
Component: rsync (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Simo Sorce
Depends On:
  Show dependency treegraph
Reported: 2005-05-19 21:12 EDT by Jamie Zawinski
Modified: 2008-08-02 19:40 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-02-16 10:01:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jamie Zawinski 2005-05-19 21:12:00 EDT
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)
    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 18:50:35 EDT
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 10:01:35 EST
No activity, close it, reopen if present in newer releases.

Note You need to log in before you can comment on or make changes to this bug.