On Thursday, April 9, 2020 at 11:01:14 PM UTC+10, Daniel Jagszent wrote: > > Hi, > > [...] I am not particularly concerned with losing 2 hours, but I am very > interested to know if this is the correct approach to have used, or if > there are better approaches. > > > PS: do you upload metadata backups every hour (i.e. you changed > --metadata-upload-interval)? Normally they get uploaded every 24 hours so > you would loose up to two days, not two hours. >
It's a mount/rsync/dismount; I'm pretty sure the unmount moves the metadata. I'd prefer every 24 hours, if that could be managed, but they are/were every hour. > > The error from fsck (apsw.ConstraintError: UNIQUE constraint failed: > contents.parent_inode, contents.name_id) means that you somehow had two > files in a directory with the same name. I have no clue how that could have > happened, since that error should have occurred the moment the second file > would have been created. If you know, how that might have happened, please > do tell so that we can try to fix S3QL to prevent these errors. > I still have a snapshot of the old bad database I think...is there a query you could suggest to find the offending record, that might jog my memory. I tried: select * from contents c join contents c1 on c1.parent_inode = c.parent_inode and c1.name_id = c.name_id and c1.rowid > c.rowid; and got a lot of rows...which is a tad scary given the constraint on the table. -- 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/3215029d-96d3-4da4-95ed-8cc00ef214e5%40googlegroups.com.
