I've described the situation further in my mail ;) Basically this is a potential bug in NixOS tarsnap module, but I wanted to make sure that I completely understand how cache directories work before diving into fixing it.
Anyway, your links are very helpful and I feel ashamed that I've overlooked this in documentation. If I understand correctly, a cache directory is bound to a key, so I need to use different cache directories for different keys -- is it correct? There's still question about first time initialization of a cache directory. Is it okay if I run fsck before the first run of tarsnap in our module automatically? On September 29, 2016 10:19:09 PM GMT+03:00, Graham Percival <[email protected]> wrote: >On Thu, Sep 29, 2016 at 10:11:57PM +0300, Nikolay Amiantov wrote: >> 1. User (me) has several tarsnap configurations with different cache >> directories and one common key file. > >What are you trying to achieve with this? I mean, what usage >scenario do you have in mind? > >I can imagine having different cache directories on separate >machines: >http://www.tarsnap.com/multiple-machines.html >although if that's what you want to do, you need to make sure the >"different" cache directories have the same contents. (see >website for details) > >There's a few more details about cache directories here: >http://www.tarsnap.com/cachedir.html > >Cheers, >- Graham -- Nikolay.
