On Wed, Jul 8, 2020 at 4:59 PM Ivan Shapovalov <[email protected]> wrote:
> On 2020-07-08 at 15:39 -0700, David Gasaway wrote: > > On Wed, Jul 8, 2020 at 6:46 AM Ivan Shapovalov <[email protected]> > > wrote: > > > > > > > This specific filesystem is used to store a borg repository. > > > > > > > I currently use borg + s3ql myself. I don't think I'd recommend > > it. In my > > experience, borg check operations don't fare well in this scenario > > (as in, > > downloads of the entire repository). I plan to switch to > > s3ql_backup.py + > > s3ql, but the prospect of the uploads needed to start from scratch > > are > > daunting. > > > > If I understand you right, then a `borg check` _has_ to download the > entire repository, because, well, it's an integrity check :) > I'm saying that borg makes certain assumptions about the repository storage space that don't necessarily mesh with the class of filesystems to which s3ql belongs. So, conditions which might be relatively unremarkable for s3ql can require a full borg check to remedy. Something may go wrong which really only impacts a single archive, a small amount of data when deduplicated, but a full repository repair is required to get borg to even recognize the issue. Find my posts on the borg mailing list if you're curious. -- -:-:- David K. Gasaway -:-:- Email: [email protected] -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/CAGsJ5AVGX-2s3D6NeGR0OMtv-MSErzP4ZWr9N1SrcD6oyKfYow%40mail.gmail.com.
