Hello Nikolaus, I was not able to find a simple way to get the file list from Cyberduck and other clients will crash after a while (there are a lot of files).
However I am inclined to think that this is a problem related to s3ql. I redid a s3qlverify with --data option and did not find any missing files. I then noticed that the missing files are always the same, such as "s3ql_data_364139". I expect that the fsck will remove them and s3ql not try again to handle them. The problem only occurs in the process of cancellation, if you load new files all works fine. One way to generate the problem is to delete all in lost + found, when I run the rm command s3ql find the missing files and do the unmount. I've tried also with s3qlrm with the same results. Do you have a more tips to handle the error? I would make sure that these missing files are marked as non-existent once and for all and s3ql will not try to recall them. Even if the Object Storage in Softlayer is not perfect, in this case it seem that is workin as aspected. I thin that I've individuated the folder that generate the error (in addition to lost+found), is there a way to delete a folder and empty lost+found directly from s3ql database? My idea is, clean the db, run fsck and (hoping) solve my problem. Thanks for your help Fabio -- 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.
