On 6/8/21 4:40 am, Frank Steinmetzger wrote: > Am Tue, Aug 03, 2021 at 10:18:06AM +0200 schrieb Frank Steinmetzger: > >>> You could delete and rebuild the cache each time (or I think there is a >>> way to do without it). >> If the cache can be easily rebuilt, then there’d be no need to store it at >> all. > Here’s an afterthought that just hit me: > there should actually be no point in archiving the cache at all. If you had > a disaster and do a full restore from borg, the old cache data becomes > invalid anyways, because the files’ inodes will now be different. AFAIK, > inodes are one way of detecting file changes. Different inode → file must be > different → rehash. > > (Unless `borg extract` updates the borg cache for files it restores, which I > doubt because the destination path is arbitrary.) > Agreed - I do get a warning on restore and my first choice is always delete the cache AND the security directory - I should just go ahead and do it anyway I guess.
Also, it would be a good time to read the borg create statement (https://borgbackup.readthedocs.io/en/stable/usage/create.html) for the file change detection parameters - moosefs and snapshots required non-default options to get it right. BillK
