Possible backup bug? Or bad backend?

Getting Help
31

@MichaelEischer You’ll be happy to know the new bitrot detection is working well in the v0.17.0 beta. I held onto that corrupted snapshot. I now get:

M?   /Volumes/Media/Photos & Videos/_To Sort/!Images/Pictures/2010/2010-08-21 (SAHS Band)/IMG_3952 [CCD356CA].JPG
M?   /Volumes/Media/Photos & Videos/_To Sort/!Images/Pictures/2010/2010-08-21 (Selfies)/IMG_0001 [2CC5C403].JPG
M?   /Volumes/Media/Photos & Videos/_To Sort/!Images/Pictures/2010/2010-08-21 (Selfies)/IMG_0003 [AC7B8288].JPG
M?   /Volumes/Media/Photos & Videos/_To Sort/!Images/Pictures/2010/2010-08-21 (Selfies)/IMG_0004 [A1A2645F].JPG
M?   /Volumes/Media/Photos & Videos/_To Sort/!Images/Pictures/2010/2010-08-21 (Selfies)/IMG_0005 [901D19E0].JPG

But if I compare the “b4_cshatag” snapshot with the “bugcheck” snapshot I ran after I found the corrupted snapshot, there’s no “M?”.

I never figured out why it happened, and as far as I know, it’s never happened again. But now I at least have a way to check by using backup --force and then diff | grep looking for “M?” lines!

4 Likes