On Mon, 1 Dec 2014, Nikolaus Rath wrote:
[snip]
I still have the bucket that was copied using the aws command line
tools, and am in the process of copying that to a new bucket for testing
so we don't lose the corrupt version, but won't get to testing it
tonight. I have not tried to use the original file system since
fsck.s3ql succeeded and am not entirely sure if it trust it without
knowing what was wrong with fsck.s3ql
At this point, I am pretty confident that this is a bug related to
object listing. Object listing is only used by fsck.s3ql, so I think
that using the file system normally (aka with mount.s3ql) should not
result in any problems.
My concern was not with the basic file system and mount.s3ql, but
rather with whether or not fsck.s3ql had correctly reconstructed the file
system after the failure given that there is (at least on occasion), a bug
in it's handling of some of the file system data.
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
