Re: Re: Can I generate a checksum for a directory?

Frank Steinmetzger <[email protected]> Mon, 9 Mar 2026 22:32:38 +0100

Newsgroups	gmane.linux.gentoo.user
Message-ID	<aa88dvZ79fTNbYgw@q>

Am Mon, Mar 09, 2026 at 04:26:49PM -0500 schrieb Dale:
> > > I could just copy Franks script over and run it for the files.  It would
> > > report any errors.  I'm sure that would take several days, maybe even a week
> > > or more, to run on all those files tho.
> > Well, to check whether a ZFS raid is still intact, one does a ZFS scrub.
> > Which is exactly what you describe: it reads everything and compares
> > checksums. On my 6 TB drives at 80 % use, it takes 10½ hours.
> > 
> 
> 
> This is what I come to figure out.  Basically, using your script is the
> easiest way.  It has to generate a checksum and compare for each file tho
> and given the huge volume of data, it would take a long while.
> 
> If you get bored, it would be nice to have a way to do the check and be able
> to resume the check.  One might have to stop more than once when checking
> large amounts of data.  Sort of like emerge does. Start a update, stop,
> resume later as needed.

It’s not really automated, but this is already possible, using the -N and -S 
option. See help output under “directory selection options”. When you press 
ctrl+c, it prints how many dirs it processed. So on the second run, add the 
option -S <number> to skip this many dirs.

-- 
Grüße | Greetings | Salut | Qapla’
Please do not share anything from, with or about me on any social network.

Operator? Please give me 911.

signature.asc (application/pgp-signature, 833 B)