On Jun 22 2016, Fabio Grasso <[email protected]> wrote:
> Il giorno mercoledì 22 giugno 2016 18:23:00 UTC+2, Nikolaus Rath ha scritto:
>>
>> > I've already tried to do an fsck, it has deleted a lot of objects that 
>> > "only exists in table but not in backend" and put a lot of files in 
>> > lost+found. If I try to mount the file system again it crashes after few 
>> > minutes. 
>> This means your backend continues to lose more data, or that it pretends 
>> to have objects (i.e., it lists their names) that it does not actually 
>> have (i.e., you can't retrieve them). There is nothing S3QL can do here. 
>>
>
> I've immediately thought to a backend problem: I had a similar case in the 
> past, but in that case opening the storage with CyberDuck show the data in 
> the backend and I received a 404 when I tried to open them. In fact it was 
> a problem that the backend then have solved after my report.
>
> Now, however, I did several tests with Cyberduck uploading, downloading and 
> deleting files and it seems that everything is working properly.

Please try the following:

 - Obtain a list of stored objects with Cyberduck
 - Run fsck.s3ql
 - Obtain a list of stored objects with Cyberduck
 - Run mount.s3ql until it fails with 404 on delete
 - Obtain a list of stored objects with Cyberduck
 - Check which of the 3 lists include the object that s3ql failed to delete
 - If it is included in the most recent one, try  to delete it with Cyberduck
 - Wait 5 minutes
 - Obtain a list of stored objects with Cyberduck

Please keep a record of all the output and the different lists. 

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.

Reply via email to