On Oct 12 2016, Nikhil Choudhary <nikh...@taligentx.com> wrote: >> On Oct 12, 2016, at 3:41 PM, Nikolaus Rath <nikol...@rath.org> wrote: >> >> So the only objects that are lost are s3ql_metadata, s3ql_passphrase >> s3ql_seq_no no? > > Hello Nikolaus, thanks for the quick response! This is correct. > >> As long as at least one s3ql_seq_no object is present, this should not >> pose a problem. > > Does the particular object matter or is any one sufficient? I > recovered s3ql_seq_no_[4,5,6,8,10,13]
Any one will do. >> If the s3ql_metadata object is missing, fsck.s3ql can recreate it from >> the .db file. You may have to comment out one or two lines in fsck.s3ql >> to deal with the complete absence of existing metadata. > > Good to hear, I looked into the patches that you’ve posted previously for > prioritizing local cache. > >> The s3ql_passphrase object can be recovered from the master key, but >> currently there is no code to do that. > > Not so good to hear, if this is the roadblock that it sounds like, I’m > in for a restoration from scratch. I'll see if I can find a few minutes to send you a patch. It shouldn't be too complicated. >> Sounds like a terrible idea. What are you trying to achieve with this? > > I’m not a fan of convoluted setups either, they seem prone to > breakage. That said, this is a way to get s3ql’s dedupe, encryption, > and caching capabilities working with ACD. Yeah, but why don't you simply use S3 instead of ACD? Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- 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 s3ql+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.