On 11/29/2014 01:36 PM, Shannon Dealy wrote: > On Sat, 29 Nov 2014, Nikolaus Rath wrote: > >> On 11/29/2014 09:49 AM, Shannon Dealy wrote: >>> Package: s3ql >>> Version: 2.11.1+dfsg-1 >>> Severity: critical >>> Justification: causes serious data loss >>> >>> Dear Maintainer, >>> >>> While running rsync to backup data to an s3ql file system mounted >>> from Amazon's >>> S3 services, the internet connection failed, resulting in the following > [snip] >> Chances are good that this can be done, so don't give up hope yet. >> >> Best, >> -Nikolaus > > Attached are both the mount and fsck log files, stripped of data from > other (irrelevent) sessions and with slight mods to remove references to > my S3 file system info (bucket/prefix). > > I have left the original bucket and local cache unmodified except for > whatever changes occured during my fsck attempt in case they can be of > use in debugging this.
Great, thanks! It seems you've actually found three issues at once: 1. mount.s3ql not coping well with a failed internet connection (a "no route to host" failure, to be precise, it copes quite well with other failures) 2. fsck.s3ql not being able to fix the local database 3. A bug somewhere that prevents you from fsck'ing a copied bucket. I'll look into this ASAP. 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.« -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org