Hi Nikolaus, On Monday, 17 June 2019 22:22:29 UTC+1, Nikolaus Rath wrote: > > On Jun 17 2019, Chris Davies <[email protected] <javascript:>> wrote: > > On Monday, 17 June 2019 19:55:47 UTC+1, Nikolaus Rath wrote: > I don't mean the log file, I mean the message that is printed on the > console where you're "being told that the S3QL filesystem is still > mounted elsewhere.". > > My best guess is that you're running fsck.s3ql / mount.s3ql with a > different --cachedir settings. Otherwise the messages that you report > don't make sense. >
Thank you for your suggestion. Unfortunately I no longer had the output of that, and I wasn't able to reproduce it. Here's why. While I was waiting for your assistance I decided to take a parallel route. Because the S3QL filesystem in this instance was being hosted on a local disk I was able to take a VM snapshot of the entire system. I removed (renamed) the zero-length s3ql_seq_no_11 file and the fsck performed flawlessly. I now have my data - and I've been able to extend by host filesystem considerably. (If this hadn't worked I would have rewound the snapshot and continued here. Clearly not an option when using a real S3-based filesystem, though.) Regards, Chris -- 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/c6a257d5-2d9c-4384-b493-ff81ca0f820f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
