Hello Viktor,

looks like either OVH has lost that file s3ql_data_1173241 or it somehow
got deleted another way. I think it will be hard to figure out what
happened (i.e. how's fault it is).

If you are willing to delete the filesystem anyways, just use Cyberduck
or a swift CLI to delete all objects in the container (or all objects
with the prefix you might be using in the container).

If you wanted to salvage what is left of this broken filesystem, you
maybe could create a dummy object in place of s3ql_data_1173241 and try
to repair the filesystem. But you would need to repair the filesystem
with the old S3QL version (that does not support Keystone v3) and since
the switch to Keystone v3 is already done according to
http://travaux.ovh.net/?do=details&id=42179 you are out of luck I suppose.



-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/s3ql/0f48c61a-44e1-e3f2-75c9-4060f8c88857%40jagszent.de.

Reply via email to