On Aug 21 2017, [email protected] wrote:
> I'll just add that repeating the fsck again without --force it said it's
> marked clean anyway.
That's because in your case fsck.s3ql aborted after the filesystem check
was complete. It failed when trying to compact the database (which
reduces disk-space usage, but doesn't change any of the contents).
Best,
-Nikolaus
--
GPG 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.
