On 3/2/26 7:17 AM, Michael wrote:
On Monday, 2 March 2026 13:08:37 Greenwich Mean Time Dale wrote:
I was hoping I could do a whole directory not each individual file. It
looks like this can't be done which may be why my searches lead
nowhere. The method you two posted is similar to what I found but
it's way to complicated for me. My command line skills isn't very
good.
There was this past thread discussing how to check a directory full of
files and a handy script provided by Frank:
https://marc.info/?t=172540602600001&r=1&w=2
I have the script Frank did and I use it. I use it to check for bitrot
or file system corruption etc. It works really well too. I do backup
the file it generates as well. Thing is, it would take a while for it
to check each individual file. There are over 64,000 files. I was
hoping it could do the whole directory in some way that is fairly
quick. The more I think on this, the more I think this can't be done,
not quickly anyway. I could at least maybe get rsync to check each new
file it transfers tho. Maybe.
I checked the rsync man page, I can't find a option for checking a
file when it is being copied over. I found a mention of checksum
that lets you tell it what checksum tool to use but can't find the
option where I tell it to do the check. Does it have a weird name
that isn't obvious as to what it does??
Thanks to you both.
Dale
:-) :-)
You need --checksum and --dry-run, AFTER you have completed your fresh
backup. It will be quicker than when it is copying files over.
I see that option now. I had to use the find tool in Konqueror tho. I
still have the drive hooked up to the NAS box, I'll boot it up and see
how long this takes. Is there a way to tell it to test just new files
it transfers? Dang, rsync has a large man page. It's not as bad as mpv
tho. o_O
Reading some more, it seems, if I read it right, that may take a while.
I'll test that tonight.
Dale
:-) :-)
