On Mon, 1 Dec 2014, Nikolaus Rath wrote:
severity -1 normal
retitle -1 fsck.s3ql sporadically crashes when checking objects
thanks
Retitling this bug and lowering severity for now. I don't think that the
mount.s3ql crash is related to the fsck.s3ql crashes, or that there is
any data corruption.
While I understand your assessment, I don't think I would characterize
this bug as "normal". Based on my understanding, the Debian guidelines
would rate this bug at the very least as "important", and frankly I would
still argue for "critical" given that it effectively "causes serious data
loss" (one of the possible criteria for "critical").
My reasoning is that even assuming the file system data has not actually
been lost or corrupted (and I believe you are likely correct in this), I
ran fsck.s3ql roughly 30 times before getting a successful run. There is
nothing to indicate that someone else with similar circumstances would not
have to run it 1000 or 100,000 more times in order to recover the file
system. For such a case, their data is unavailable to them and
effectively 100% lost until they have a fixed version of fsck.s3ql
FWIW.
Shannon C. Dealy | DeaTech Research Inc.
de...@deatech.com | - Custom Software Development -
USA Phone: +1 800-467-5820 | - Natural Building Instruction -
numbers : +1 541-929-4089 | www.deatech.com
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
