On 6 February 2017 at 13:31, Daniel Jagszent <[email protected]> wrote:
> Hello Ketil,
>
> Ketil Froyn schrieb:
>
> (By the way, I ran the command "s3qlctrl log ~/storage/ debug"
> yesterday, as mentioned. That appears to be hanging still.)
>
> https://bitbucket.org/nikratio/s3ql/issues/143/s3qlctrl-log-broken
> This would probably not happen with a more recent version of S3QL.

Thanks for the details. That may be what had bitten me next. My
unmount finally completed, but with an exception:

$ umount.s3ql storage/
Uncaught top-level exception:
Traceback (most recent call last):
  File "/usr/bin/umount.s3ql", line 9, in <module>
    load_entry_point('s3ql==2.15', 'console_scripts', 'umount.s3ql')()
  File "/usr/lib/s3ql/s3ql/umount.py", line 183, in main
    blocking_umount(options.mountpoint)
  File "/usr/lib/s3ql/s3ql/umount.py", line 122, in blocking_umount
    pid = parse_literal(llfuse.getxattr(ctrlfile, 's3ql_pid?'), int)
  File "src/llfuse/fuse_api.pxi", line 211, in llfuse.capi.getxattr
(src/llfuse/capi_linux.c:25382)
OSError: [Errno 107] Transport endpoint is not connected:
'storage/.__s3ql__ctrl__'

In the meantime, my s3qlctrl also crashed:

$ s3qlctrl log storage/ debug
Uncaught top-level exception:
Traceback (most recent call last):
  File "/usr/bin/s3qlctrl", line 9, in <module>
    load_entry_point('s3ql==2.15', 'console_scripts', 's3qlctrl')()
  File "/usr/lib/s3ql/s3ql/ctrl.py", line 93, in main
    llfuse.setxattr(ctrlfile, 'logging', cmd)
  File "src/llfuse/fuse_api.pxi", line 119, in llfuse.capi.setxattr
(src/llfuse/capi_linux.c:24633)
OSError: [Errno 5] Input/output error: 'storage/.__s3ql__ctrl__'


And then the mount seemed to be borked:

$ s3qlstat storage/
File system appears to have crashed.

I managed to fix it with:

$ fusermount -u storage
$ fsck.s3ql s3://<bucket>
$ mount.s3ql s3://<bucket> storage

Regards, Ketil

-- 
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