retitle 596857 sftp backend falsely reports success on r/o filesystem forwarded 596857 https://bugs.launchpad.net/duplicity/+bug/638629 severity 596857 normal thanks
On Tue, 14 Sep 2010 17:41:19 +0200, Marian Sigler writes: >When the remote backup dir is on a read-only filesystem, duplicity does >not report any errors. It does not create the files (of course), but >reports success and exits with 0 i can confirm this, but only if you use the sftp (not scp) backend. >However, if GPG is not used (--no-encryption), it does print warnings >and exits with 1. your second run fails more visibly not because of the encryption option but rather because a different metadata cache state (~/.cache): the encryption isn't relevant. if you nuke the cache beforehand (to cause a full backup) you get the very same false ok with --no-encryption. i've forwarded this upstream, but am lowering the severity as this is bad but not critical. the common-sense work around of not mounting a backup filesystem read-only works fine, there's a secondary work around: --use-scp. furthermore, the more common problem scenario (insufficient permissions on the target) does not trigger this silent failure behaviour. regards az -- + Alexander Zangerl + DSA 42BD645D + (RSA 5B586291) Actually, we have scientifically determined that Heisenberg did indeed sleep exactly here. However, we have no idea whatsoever just how fast asleep he was. -- Dave Aronson
signature.asc
Description: Digital Signature
