On Jun 22 2016, Fabio Grasso <[email protected]> wrote:
> Hello,
> I've a problem with an S3QL file system. It contiously umount due to 404
> error:
>
> 2016-06-22 11:15:02.493 10482:Thread-12 root.excepthook: Uncaught top-level
> exception:
> Traceback (most recent call last):
> File
> "/usr/lib64/python3.4/site-packages/s3ql-2.18-py3.4-linux-x86_64.egg/s3ql/backends/swift.py",
>
> line 387, in delete
> resp = self._do_request('DELETE', '/%s%s' % (self.prefix, key))
> File
> "/usr/lib64/python3.4/site-packages/s3ql-2.18-py3.4-linux-x86_64.egg/s3ql/backends/swift.py",
>
> line 251, in _do_request
> raise HTTPError(resp.status, resp.reason, resp.headers)
> s3ql.backends.s3c.HTTPError: 404 Not Found
[...]
This means your backend has lost data.
> 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 runned s3ql_verify but it haven't found corrupted or missing
> objects.
This is quite unlikely. The only explanation that I have is that you hit
a "lucky window" right after an fsck, and that at this point mount.s3ql
would have worked as well.
Did you run it with our without --data?
In any case, my suggestion is to switch to a different storage
provider. Copy the raw backend data over using some other tool, and then
run fsck.s3ql + s3ql_verify on the new backend. After that, mount.s3ql
should work fine.
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.
