Hi everybody!
I'm willing to debug this bug, could you please give me the theorical ways
this bug could happen, so that I can search more efficiently for the reason
of the bug?
--> SQL 3.3.2 (I know, cannot upgrade right now)
--> Happened on 6 of ~200 S3QL instances I manage
--> Openstack OVH backend
--> fsck.s3ql does not fix the issue, will happen again at some random time
later
2020-08-12 09:54:14.716 5090:fuse-worker-9 root.excepthook: Uncaught
top-level exception:
Traceback (most recent call last):
File "/data/s3ql/src/s3ql/inode_cache.py", line 92, in __del__
raise RuntimeError('BUG ALERT: Dirty inode was destroyed!')
RuntimeError: BUG ALERT: Dirty inode was destroyed!
2020-08-12 09:54:15.006 5090:MainThread s3ql.mount.unmount: Unmounting file
system...
2020-08-12 09:54:15.141 5090:MainThread root.excepthook: Uncaught top-level
exception:
Traceback (most recent call last):
File "/data/s3ql/bin/mount.s3ql", line 21, in <module>
s3ql.mount.main(sys.argv[1:])
File "/data/s3ql/src/s3ql/mount.py", line 214, in main
raise RuntimeError('Received signal %d, terminating' % (ret,))
Thanks a lot!
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/a7bb585f-1753-4f57-8134-a5f84a933086n%40googlegroups.com.
