Hello! Sorry, it seems a previous answer did not go through. Thank you for your answer.
> --> SQL 3.3.2 (I know, cannot upgrade right now) > You might want to first upgrade before diving into debugging this issue. > Since newer versions of S3QL use pyfuse3 instead of llfuse and also use > a newer trio versions it might very well be that your bug has vanished > in newer S3QL versions. Ok I did the upgrade to SQL 3.5.0 last week. --> The bug is still present (had one occurence in a week since the upgrade) --> BUT the filesystem no longer crash, which is good. S3QL somehow manages to delete/garbage collects an _Inode object that is > dirty (i.e. has an attribute modification that is not persisted in the > S3QL database) > So, if I understand correctly, since it is a pending modification on a now deleted inode, this is not really a problem, right? Said otherwise, the filesystem is not corrupted? If the filesystem is not corrupted, and it now no longer crashes, I can live with that :-) Thank you, Nicolas Deschildre -- 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 s3ql+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/7e6316d6-4f07-4c56-a402-bd2f28bd9947n%40googlegroups.com.
