Nikolaus, My s3ql Version is 2.11.1 ( in my message header ). I did try fsck with -f ( force ) with the same result as below.
The console output gives the "still mounted" message then just drops back to a prompt...... Here's the output: Starting fsck of s3://winglernas1/fileserver Backend reports that file system is still mounted elsewhere. Either the file system has not been unmounted cleanly or the data has not yet propagated through the backend. In the later case, waiting for a while should fix the problem, in the former case you should try to run fsck on the computer where the file system has been mounted most recently. Enter "continue" to use the outdated data anyway: > pi@raspberrypi:/ $ On Friday, July 7, 2017 at 4:57:45 AM UTC-7, Nikolaus Rath wrote: > > On Jul 06 2017, Todd Wingler <[email protected] <javascript:>> wrote: > > I'm trying to run fsck on my S3 bucket, in order to be able to mount it. > > Background - My Pi filesystem folder became corrupt and raspian was > > unresponsive. I tried to recover the filesystem folder, but it was too > > corrupt, so I reinstalled a fresh OS image. I'm not certain which > version > > was previosly installed on my corrupt image, but it was in just > installed > > in Mar, 2017....not too long ago. Upon mounting my S3 bucket on new OS > > image, mount complained it was already mounted elsewhere. I ran fsck > > multiple times, but just get this in my log. It seems to error out with > no > > errorcode, just excepthook: > > What is your S3QL version? > What is the output of fsck.s3ql (not the log, the console output)? > Have you tried running with -f? > > Best, > -Nikolaus > > -- > GPG 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.
