It's not generally recommended to run --fsck before every archive, because it downloads all metadata for your archives, which is approximately 0.1% of the total size. https://www.tarsnap.com/cachedir.html
However, --fsck is a good thing to try if you encounter an error, and was absolutely the right thing to do in this case. Cheers, - Graham Percival On Tue, Aug 31, 2021 at 12:55:50PM -0500, J. Hellenthal via tarsnap-users wrote: > > Definitely related to the problem that seems to be a miscommunication or > calculation on the cache directory itself. > > Personally I make it a habit to run an fsck before a backup just to be sure > things like this don't happen and then if it does you still have the cache to > explore when it does. > > -- > J. Hellenthal > > The fact that there's a highway to Hell but only a stairway to Heaven says a > lot about anticipated traffic volume. > > > On Aug 31, 2021, at 11:48, Matthias Güdemann <[email protected]> wrote: > > > > > >> > >> Have you attempted to --fsck ? > > > > I have now and it worked. Thanks for the hint! > > Is this specific to this problem or generally a good idea to try first > > in case of a problem? > > > > Best regards > > Matthias
