> There is no error in mount.log [...] That's quite unusual. S3QL will almost always log exceptions. If the only difference is that you use WIFI instead of a cable when S3QL crashes I do not think it's that special that S3QL would not log an exception. How do you start mount.s3ql? Maybe you disabled mount.log logging altogether? > [...]I usually don't want to continue using a file system after such > an error because I'm thinking it might be corrupted in unknown and > unfixable ways (even by fsck). It's quite safe that you use a S3QL filesystem after a crash. I have some S3QL filesystems running since 2013. They have crashed several times thru the years. They always could be repaired with fsck. But always run fsck on the machine that crashed. (since this machine has the up-to-date SQlite database that you need)
-- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/a0c6040d-a3ef-997f-0928-df62e542a982%40jagszent.de.
