On 12/03/2014 11:44 PM, Shannon Dealy wrote:
the file system still hangs (or the next time it hangs), could you
>> follow the instructions at
>> https://bitbucket.org/nikratio/s3ql/wiki/Providing%20Debugging%20Info to
>> obtain a Python stacktrace, and attach it to this issue?
>
> This time the file system didn't hang until I attempted to unmount it.
> Attached are two log files with the mount and stack trace information.
This looks odd. Did you issue both "setfattr -n fuse_stacktrace" *and*
"kill -s USR1" commands?
The attached files indicate both, and moreover, the number of active
threads during the "kill -s USR1" command was much lower than during the
"setfattr" command. How much time did pass between these commands
(assuming that you issued both)?
At least at the time that you issued the "kill" command, mount.s3ql was
busy doing the SSL handshake with the remote server, so while it looked
like it was hanging, it was probably waiting for the remote server.
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.«
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
