| Newsgroups |
gmane.comp.audio.eac.user |
| Message-ID |
<CANm05mQrg2qtp7ckUYUG1PbCzZ5gyb8RU1EMqejp9vFguFxszA@mail.gmail.com> |
On Thu, Oct 1, 2020 at 2:15 PM Fred Maxwell [email protected]
[EAC] <[email protected]> wrote:
>
>
> That’s also a great method. Did you mean "find *" or was that supposed to
> be "find .” to begin the search at the current directory?
>
> I made some tweaks and came up with this Mac-friendly method:
>
> find . -type f -exec shasum -a 256 '{}' \; > sha256.txt
> shasum -a 256 -c sha256.txt | grep FAILED
>
> Notes:
> 1. md5sum is not installed by default on the Mac, but shasum is and
> SHA256 is more robust.
> 2. My music directory tree has multiple formats of music as well as
> ancillary files like cover art, so I opened it up to all files.
> 3. I don’t want to see thousands of “OK” lines, so I added the grep for
> “FAILED”. I’m hoping I don’t encounter an artist, album, or track name
> that contains “FAILED”. :)
>
md5sum allows the --quiet switch so only those lines that don't match
(including " not found") are actually printed; does shasum have a similar
switch? Then you wouldn't need the grep, and you'd see all failures, for
whatever reason.
4. Your method with date-specific filenames makes sense, but I was being
> lazy.
> 5. My version assumes that your current working directory (as in ‘pwd’)
> is the top level of your music directory structure when you start. The
> find could be modified to specify that directory.
>
> Thanks, Jerry.
>
> On Oct 1, 2020, at 1:14 PM, Jerry Baker jbaker6953-/[email protected] [EAC] <
> [email protected]> wrote:
>
> I like to do a recursive md5sum (or sha256sum):
>
> find * -name *.flac -exec md5sum {} ; > flacmd5_20201001.txt
>
> The resulting file is portable. I can take it to any mirror of my music
> and use "md5sum -c flacmd5_20201001.txt" to verify that mirror is
> identical to the other. An added bonus is that it's a snapshot in time
> so I can verify that the files are the same today as they were last year.
>
> On 10/1/2020 9:46 AM, Fred Maxwell [email protected]
> <[email protected]> [EAC] wrote:
> > diff -rqx '.*’ directory1/ directory2/
> >
> > {I’m assuming that you have at least two copies of your music collection
>
> > and that you have diff}
> >
> > > so it's very much a deal breaker for me. It took me 18 months to get
> > all my CDs online, which made me pretty fussy about it.
> >
> > How many bit flips within FLAC files has your code detected?
> >
> > If you’re seeing bit flips in files, whether FLAC, executable, OS, or
> > anything else, you have issues with your storage subsystem that need to
> > be addressed.
> >
> > My music (primarily in ALAC) is stored on a eight drive RAID-6 NAS that
> > performs regular scrubbing (parity checking). I have confidence in the
> > data integrity of all files stored on that NAS, including the music
> > files. Of course, that is not my only copy of my music (or any other
> files).
> >
> > Regards,
> > Fred Maxwell
> > Moderator, Exact Audio Copy Yahoogroup
>
>
--
It is hard to believe a man is telling you the truth when you know you
would lie if you were in his place.
-- H.L. Mencken