Debian Bug report logs - #607234
Ignores failure to write, continues stupidly

Reply or subscribe to this bug.

Display info messages

Message #5 received at [email protected] (full text, mbox, reply):

From: martin f krafft <[email protected]>

To: Debian Bug Tracking System <[email protected]>

Subject: Ignores failure to write, continues stupidly

Date: Thu, 16 Dec 2010 01:04:53 +0100

[Message part 1 (text/plain, inline)]

Package: rsync
Version: 3.0.7-2
Severity: normal

This is possibly related to #595967.

Last week I set off an rsync job of several terabytes of data and
then rushed to catch a train. On return, I found the target empty,
and yet the rsync was still running. The reason was insufficient
permissions to write to the target. Meanwhile, rsync burned
resources for nothing.

If rsync fails to write a file, why continue to read and transfer
the file? Shouldn't the protocol abort (and rsync exit with
failure)?

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.36-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages rsync depends on:
ii  base-files                    5.9        Debian base system miscellaneous f
ii  libacl1                       2.2.49-4   Access control list shared library
ii  libc6                         2.11.2-7   Embedded GNU C Library: Shared lib
ii  libpopt0                      1.16-1     lib for parsing cmdline parameters
ii  lsb-base                      3.2-26     Linux Standard Base 3.2 init scrip

rsync recommends no packages.

Versions of packages rsync suggests:
ii  openssh-client                1:5.6p1-2  secure shell (SSH) client, for sec
ii  openssh-server                1:5.6p1-2  secure shell (SSH) server, for sec

-- no debconf information


-- 
 .''`.   martin f. krafft <[email protected]>      Related projects:
: :'  :  proud Debian developer               http://debiansystem.info
`. `'`   http://people.debian.org/~madduck    http://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems

[digital_signature_gpg.asc (application/pgp-signature, inline)]

Message #10 received at [email protected] (full text, mbox, reply):

From: Toni Mueller <[email protected]>

To: [email protected]

Subject: problem persists in Stretch, upgrade severity?

Date: Sun, 12 Mar 2017 14:53:54 +0100

Hi,

I can say that this problem persists in Stretch. I also went to copy a
lot of files to another machine, then went away, and found that rsync
was happily claiming to have written files correctly (I used -azvvcP),
but the target directory was empty.

This was with rsync 3.1.2-1 on amd64 on the sender side (Stretch), and
rsync 3.1.1-3 amd64 on the receiver side (Jessie).

I have ext4 file systems on both sides of the copy operation.

I think this bug should be upgraded to 'serious', since it could easily
result in data loss if the sender would delete files after transfer on
the sendind side.


Cheers,
--Toni++

Send a report that this bug log contains spam.