Heya, Happy new year for everyone
After keeping s3ql weeks or days mounted, it always fail to umount, only
way i have manageg to fix this is remount drives time to time, is there any
other tip what i can fix this?
now after 16days (uptime of server was last time mounted) it fails again,
last time i though done something wrong, but now this repeates again.
only way is force umount and then after fsck. this happens as well to
local:// filesystem and swift:// one.
:~# /root/s3ql/s3ql-2.15/bin/umount.s3ql --debug /mnt/s3ql/Musiikkivideot
2016-01-02 17:08:36.196 25817 MainThread s3ql.umount.blocking_umount:
Flushing cache...
2016-01-02 17:08:36.222 25817 MainThread s3ql.umount.blocking_umount:
Trying to get pid
2016-01-02 17:08:36.223 25817 MainThread s3ql.umount.blocking_umount: PID
is 11348
2016-01-02 17:08:36.234 25817 MainThread s3ql.umount.blocking_umount:
Unmounting...
2016-01-02 17:08:36.256 25817 MainThread s3ql.umount.blocking_umount:
Uploading metadata...
2016-01-02 17:08:36.268 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:36.269 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:36.380 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:36.380 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:36.592 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:36.592 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:36.905 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:36.905 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:37.317 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:37.318 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:37.828 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:37.829 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:38.440 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:38.440 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:39.152 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:39.152 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:39.963 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:39.964 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:40.875 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:40.875 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:41.887 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:41.888 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:42.999 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:43.000 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:44.111 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:44.112 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:45.224 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:45.224 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:46.335 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:46.335 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:47.449 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:47.449 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:48.561 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:48.562 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:49.673 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:49.674 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:50.786 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:50.786 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:51.898 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:51.898 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:53.010 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:53.011 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:54.122 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:54.123 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:08:55.234 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:08:55.235 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
.........
2016-01-02 17:14:02.436 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:14:02.437 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
2016-01-02 17:14:03.548 25817 MainThread s3ql.umount.blocking_umount: PID
still alive and commandline unchanged.
2016-01-02 17:14:03.549 25817 MainThread s3ql.umount.blocking_umount:
Daemon seems to be alive, waiting...
^C2016-01-02 17:14:04.244 25817 MainThread root.excepthook: Uncaught
top-level exception:
Traceback (most recent call last):
File "/root/s3ql/s3ql-2.15/bin/umount.s3ql", line 26, in <module>
s3ql.umount.main(sys.argv[1:])
File "/root/s3ql/s3ql-2.15/src/s3ql/umount.py", line 183, in main
blocking_umount(options.mountpoint)
File "/root/s3ql/s3ql-2.15/src/s3ql/umount.py", line 164, in
blocking_umount
time.sleep(step)
KeyboardInterrupt
It just loops, see time how log i waited. the filesystem was not on use,
check with lsof and every process has killed.
So any tips? :) maybe cron remount drives every day, but then if i left
file transfer overnight it will fail.
--
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.
