<div dir="ltr">Ok, thank you for this extra info. I have experienced exactly what you described. The rsync dry run is _still_ running after being started at 1:30am PST :)<div><br></div><div>But it is finding the right files to update. Most of the entries are:</div><div>
<p class=""><span class="">>fc........</span></p><p class="">Which is what I want.</p><p class="">So, just because I see:</p><p class="">>f</p><p class="">at the beginning...</p><p class="">That doesn't necessarily mean that the file is going to get updated at the destination? In other words, you're saying that just doing the delta transfer is more time efficient and rsync won't touch the file unless _some_ relevant change is observed? It just concerned me because the file list was extensive, and I definitely don't want anything copied unless for example the checksums don't match.</p><p class="">Thanks,</p><p class="">-Clint</p></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 28, 2015 at 5:41 AM, Kevin Korb <span dir="ltr"><<a href="mailto:kmk@sanitarium.net" target="_blank">kmk@sanitarium.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
</span>- --checksum generally takes a lot longer than --size-only. A delta<br>
transfer generally goes quicker than a checksum. However, if you want<br>
to make a list of what is corrupt a checksumming utility that is less<br>
stupid than rsync can be useful. I say that because rsync's<br>
- --checksum is entirely unintelligent. It will checksum every single<br>
file on both ends including files that only exist on one end and files<br>
that shouldn't match (the size is wrong). At the end of --checksum<br>
you will still have to do the delta xfers that you would do without it.<br>
<br>
OTOH, you are using --dry-run. If you are trying to generate a report<br>
about what files are corrupted then only --checksum an do that. It<br>
will just do it in the dumbest/slowest way possible.<br>
<span class=""><br>
On 10/28/2015 02:08 AM, Clint Olsen wrote:<br>
> What about -c? It seems I'm getting a lot of spurious file<br>
> transfer candidates when using:<br>
><br>
> -avvznIi --no-o --no-g --no-p<br>
><br>
> It's showing transfers (receive) for many files I know haven't<br>
> been tampered with.<br>
><br>
> Thanks,<br>
><br>
> -Clint<br>
><br>
> On Tue, Oct 27, 2015 at 7:53 PM, Kevin Korb <<a href="mailto:kmk@sanitarium.net">kmk@sanitarium.net</a><br>
</span><span class="">> <mailto:<a href="mailto:kmk@sanitarium.net">kmk@sanitarium.net</a>>> wrote:<br>
><br>
> That is correct. Rsync will re-copy (delta xfer unless<br>
> --wholefile) all the files. You can always --dry-run if you aren't<br>
> sure.<br>
><br>
> On 10/27/2015 10:07 PM, Clint Olsen wrote:<br>
>> Hi:<br>
><br>
>> I've been using rsync to create backups for a few years. A few<br>
>> months ago I started experiencing sector errors. I ended up<br>
>> replacing the drive and copying the drive data. It turns out<br>
>> that due to the default behavior of rsync "quick check", some of<br>
>> the files were modified without altering the modification time or<br>
>> size, so these files are still clean in the backup. I would like<br>
>> to recover these files, but I need to defeat the quick check in<br>
>> order to do this. It looks like using:<br>
><br>
>> -I, --ignore-times don't skip files that match size and<br>
>> time<br>
><br>
>> will work. I just want to confirm that this covers it. The<br>
>> long-form of the switch doesn't mention size, so I was concerned<br>
>> this was the right way to accomplish this. If there are any<br>
>> other switches that would be useful in the context of potentially<br>
>> corrupt files, please feel free to chime in...<br>
><br>
>> Thanks,<br>
><br>
>> -Clint<br>
><br>
><br>
><br>
><br>
><br>
</span><span class="">> -- Please use reply-all for most replies to avoid omitting the<br>
> mailing list. To unsubscribe or change options:<br>
> <a href="https://lists.samba.org/mailman/listinfo/rsync" rel="noreferrer" target="_blank">https://lists.samba.org/mailman/listinfo/rsync</a> Before posting,<br>
> read: <a href="http://www.catb.org/~esr/faqs/smart-questions.html" rel="noreferrer" target="_blank">http://www.catb.org/~esr/faqs/smart-questions.html</a><br>
><br>
><br>
><br>
><br>
<br>
</span><span class="">- --<br>
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,<br>
- -*~<br>
Kevin Korb Phone: <a href="tel:%28407%29%20252-6853" value="+14072526853">(407) 252-6853</a><br>
Systems Administrator Internet:<br>
FutureQuest, Inc. Kevin@FutureQuest.net (work)<br>
Orlando, Florida <a href="mailto:kmk@sanitarium.net">kmk@sanitarium.net</a> (personal)<br>
Web page: <a href="http://www.sanitarium.net/" rel="noreferrer" target="_blank">http://www.sanitarium.net/</a><br>
PGP public key available on web site.<br>
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,<br>
- -*~<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v2<br>
<br>
</span>iEYEARECAAYFAlYwwnoACgkQVKC1jlbQAQfHMACfXgY160iVto4Sm5tN7gv+QL39<br>
8DsAn3hvPbx3kunv1DIlC9BRXdSVD9fn<br>
=xDso<br>
<div class="HOEnZb"><div class="h5">-----END PGP SIGNATURE-----<br>
<br>
--<br>
Please use reply-all for most replies to avoid omitting the mailing list.<br>
To unsubscribe or change options: <a href="https://lists.samba.org/mailman/listinfo/rsync" rel="noreferrer" target="_blank">https://lists.samba.org/mailman/listinfo/rsync</a><br>
Before posting, read: <a href="http://www.catb.org/~esr/faqs/smart-questions.html" rel="noreferrer" target="_blank">http://www.catb.org/~esr/faqs/smart-questions.html</a><br>
</div></div></blockquote></div><br></div>