Nicola Cocchiaro <[email protected]> writes:
> Nikolaus,
>
> A while ago we had discussed an llfuse exception in a thread called 
> "strange llfuse exception" that was not being correctly formed due to a 
> Cython bug. With the workaround in llfuse 0.40 the issue with the exception 
> was resolved, but the same triggering event of Google Storage returning 403 
> intermittently still triggers an exception that results in bad behavior. 
> Specifically, after an AccessDenied exception (or two as in the logs 
> below), mount.s3ql hangs and with it all file system operations also hang 
> (e.g., accessing the file system extended attributes or running the 'ls' 
> and 'df' commands).
[...]
>
> This triggers another AccessDenied exception, but that's where the log 
> ends. At this point S3ql is no longer responsive, 'ls' and 'df' hang, and 
> any other file system operation also seems to hang. This also happened 
> consistently with all S3ql processes I had running on other boxes that 
> happened to be uploading data in the time window when Google intermittently 
> returned 403.

Thanks for the report. I'll try to reason out what's happening
here. Could you please report this issue at
https://bitbucket.org/nikratio/s3ql/issues to make sure it doesn't get
lost?

Also, if you can reproduce this issue (or encounter it again) and
mount.s3ql hangs, could you please try to obtain a Python stacktrace as
explained on
https://bitbucket.org/nikratio/s3ql/wiki/Providing%20Debugging%20Info?
That'd make it much easier to diagnoses what's going on.


> Question is, is this due to the timing of those (repeated) exceptions and 
> how S3ql handles them, or a FUSE bug?

No, this is probably an S3QL bug.

Best,
Nikolaus

-- 
Encrypted emails preferred.
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6  02CF A9AD B7F8 AE4E 425C

             »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/groups/opt_out.

Reply via email to