DO NOT REPLY [Bug 3653] Reduce the need for the vanished files warning
https://bugzilla.samba.org/show_bug.cgi?id=3653 --- Comment #19 from m...@mattmccutchen.net 2010-11-21 17:57 CST --- (In reply to comment #18) What's also annoying is that a vanished file warning triggers: IO error encountered -- skipping file deletion which if I'm not mistaken stops *all* files from being deleted on the receiving end, not just the ones that have vanished. You're right that the IOERR_GENERAL flag (which corresponds to that message) stops all destination files from being deleted. But it is only supposed be set when there is an error that might lead to the omission of existing source files from the file list. A run-of-the-mill vanished file should not set the flag. If you have a reproducible case in which it does, please file a separate bug. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 3653] Reduce the need for the vanished files warning
https://bugzilla.samba.org/show_bug.cgi?id=3653 jr-sambabugzi...@quo.to changed: What|Removed |Added CC||jr-sambabugzi...@quo.to --- Comment #18 from jr-sambabugzi...@quo.to 2010-11-20 12:47 CST --- +1 for --ignore-vanished. Filtering out the warnings when stdout and stderr are redirected to different places isn't so trivial. What's also annoying is that a vanished file warning triggers: IO error encountered -- skipping file deletion which if I'm not mistaken stops *all* files from being deleted on the receiving end, not just the ones that have vanished. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 3653] Reduce the need for the vanished files warning
https://bugzilla.samba.org/show_bug.cgi?id=3653 j...@jwz.org changed: What|Removed |Added CC||j...@jwz.org --- Comment #17 from j...@jwz.org 2010-10-01 11:27 CST --- Me too. Doing nightly backups from cron is an *extremely* common use-case of rsync, and telling each and every user of rsync that they should either A) write their own shell script to filter and discard error messages, or B) play a constant game of whack-a-mole chasing down new --exclude options to add, is just silly. It pushes work downstream that could be done upstream much more efficiently. Why make each user write the same code over and over when the developer could write it just once, and get it right? Option A is bad because everyone gets to introduce differently-subtle bugs in their script (wrong error code? accidentally ignoring too many error messages? who knows. It's fragile.) Option B is bad because I don't *want* to have a bunch of --exclude options for my backup: disk and bandwidth are cheap, so I want my backup disk to be an exact mirror. That way, when the disk holding / dies, I can just drop the backup in and boot it, being confident that everything is exactly the same. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 3653] Reduce the need for the vanished files warning
https://bugzilla.samba.org/show_bug.cgi?id=3653 r...@golder.org changed: What|Removed |Added CC||r...@golder.org --- Comment #16 from r...@golder.org 2009-05-18 07:59 CST --- This is a 'me too' for '--ignore-vanished-files' flag. Lots of legitimate cases where files could vanish, so having the option to treat this as normal (i.e. prevent rsync from producing this warning and ensure a zero exit value) should be simple enough, and would prevent lots of people (me included) from needing to use wrapper scripts, hacks and/or just give it to receiving the annoying cron messages it causes :) -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 3653] Reduce the need for the vanished files warning
https://bugzilla.samba.org/show_bug.cgi?id=3653 --- Comment #14 from rv-rsyncbugzi...@eychenne.org 2009-04-22 03:39 CST --- I also find this warning annoying, I really vote for this patch. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 3653] Reduce the need for the vanished files warning
https://bugzilla.samba.org/show_bug.cgi?id=3653 --- Comment #15 from o...@yadan.net 2009-04-22 03:51 CST --- I ended up using the following script for snapback2 (which exits with the same error codes as rsync if rsync fails: # cat /etc/cron.daily/snapback2 #! /bin/sh OUT=`/usr/bin/snapback2 21` RET=$? if [ $RET != 23 -a $RET != 0 -a $RET != 24 ]; then echo $OUT exit $RET fi this is a workaround, it would still be great to be able to tell rsync to ignore vanished files. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 3653] Reduce the need for the vanished files warning
https://bugzilla.samba.org/show_bug.cgi?id=3653 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #13 from [EMAIL PROTECTED] 2008-07-14 16:24 CST --- Guys, I also find this warning annoying. I get a pretty much daily email about it from my backup 'failing'. /etc/cron.daily/snapback2: rsync warning: some files vanished before they could be transferred (code 24) at main.c(1515) [generator=3.0.2] I am not even sure which files are vanishing. I suspect the files are from a mail directory, where some spam messages are moved after rsync builds the files list. I vote for including the patch into rsync to make it more useful for this use case. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
