Re: fsck required after startup on Mac

[Colin Percival <cperciva@tarsnap.com>]

On 9/15/22 11:18, Graham Percival wrote:
> Assuming that's not the case, I would try making a copy of your cache
> directory, or at least recording the directory listing.  For example,
> right now my casual "garbage test tarsnap" cachedir is:
>
> $ ls -l ~/.test-tarsnap/cache/
> total 76
> -rw-r--r--  1 td  td    103 May 13 12:26 cache
> lrwxr-xr-x  1 td  td     64 May 13 12:26 cseq -> 5c10f4d39bc2508073a02cc8710821800f5f970d1255497f53d493e58dc399da
> -rw-r--r--  1 td  td  72264 May 13 12:26 directory
> -rw-r--r--  1 td  td      0 May 13 12:20 lockf
>
> If I checked that in a day or two and found different dates and cseq (without
> myself consciously making a new archive), that would be very weird.
The other possibility which comes to my mind is that MacOS might be deleting
the cache directory when you reboot.  You don't want to put it into /tmp/,
for example...

--
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid