On Oct 08 2015, Chris Croome <[email protected]> wrote: > Checking blocks (refcounts)... > Checking blocks (checksums)... > No cached checksum for block 113265, recomputing... > Dropping temporary indices... > Uncaught top-level exception: > Traceback (most recent call last): > File "/usr/bin/fsck.s3ql", line 9, in <module> > load_entry_point('s3ql==2.13', 'console_scripts', 'fsck.s3ql')() > File "/usr/lib/s3ql/s3ql/fsck.py", line 1274, in main > fsck.check() > File "/usr/lib/s3ql/s3ql/fsck.py", line 95, in check > self.check_blocks_checksum() > File "/usr/lib/s3ql/s3ql/fsck.py", line 668, in check_blocks_checksum > (hash_, block_id)) > File "/usr/lib/s3ql/s3ql/database.py", line 98, in execute > self.conn.cursor().execute(*a, **kw) > File "src/cursor.c", line 236, in resetcursor > apsw.ConstraintError: ConstraintError: UNIQUE constraint failed: blocks.hash > > Any suggestions what I could try to resolve this?
Looks like you hit a rare corner case that reveals a bug in S3QL. Please report it at https://bitbucket.org/nikratio/s3ql/issues. 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
