On Apr 03 2016, Ryan Groth <[email protected]> wrote: > Hello, > > Using s3ql 2.17.1 - > > Apr 1 20:16:08 lsaws-backup journal: mount.s3ql[14791:fuse-worker-25] > root.excepthook: Uncaught top-level exception: > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/site-packages/s3ql-2.17.1-py3.5-linux-x86_64.egg/s3ql/inode_cache.py", > line 92, in __del__ > raise RuntimeError('BUG ALERT: Dirty inode was destroyed!') > RuntimeError: BUG ALERT: Dirty inode was destroyed! > Apr 1 20:16:15 lsaws-backup journal: mount.s3ql[14791:MainThread] > s3ql.mount.unmount: Unmounting file system... > > Any thoughts on cause/fix? Other than the unfixed but documented SSL > BAD_WRITE_RETRY, I have not an issue up to this - thanks for the great > software!
https://bitbucket.org/nikratio/s3ql/issues/204/mounts3ql-occasionally-dies-with-bug-alert I hope to be able to look into this next week. Please ping the bug I you don't see any response by then. 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.
