On Sep 01 2015, Donny Ward <[email protected]> wrote:
> Hello,
>
> I have an external hard drive (exFAT) with an s3ql filesystem stored on it 
> with about 600GB. I plugged in this external hard drive and mounted its 
> s3ql filesystem in order to copy everything off the disk. I left my 
> computer on overnight and when I woke up I found out that my computer died 
> (well, it just froze, I had to power it off and on). Now I'm trying to 
> mount the s3ql filesystem again and it says I need to run fsck.s3ql first. 
> So I did that.
>
> There were several "Committing block 0 of inode 2967 to backend" type 
> messages.

In that case you must have modified files in the S3QL file system, and
not just copied files from it.

> Eventually fsck died though. I would restart fsck and it would 
> commit more inodes before dying again. Now fsck dies immediately, and here 
> is the output.
>
> donny@donny-lubuntu:~$ fsck.s3ql local:///media/donny/WDBLACK/s3ql/
> Enter file system encryption passphrase: 
> Starting fsck of local:///media/donny/WDBLACK/s3ql
> Using cached metadata.
> Remote metadata is outdated.
> Checking DB integrity...
> Creating temporary extra indices...
> Checking lost+found...
> Checking cached objects...
> Committing block 0 of inode 2967 to backend
> Dropping temporary indices...
> Uncaught top-level exception:
> Traceback (most recent call last):
>   File "/usr/bin/fsck.s3ql", line 9, in <module>
>     load_entry_point('s3ql==2.13', 'console_scripts', 'fsck.s3ql')()
>   File "/usr/lib/s3ql/s3ql/fsck.py", line 1272, in main
>     fsck.check()
>   File "/usr/lib/s3ql/s3ql/fsck.py", line 81, in check
>     self.check_cache()
>   File "/usr/lib/s3ql/s3ql/fsck.py", line 179, in check_cache
>     hash_ = sha256_fh(fh)
>   File "/usr/lib/s3ql/s3ql/common.py", line 220, in sha256_fh
>     buf = fh.read(BUFSIZE)
> OSError: [Errno 5] Input/output error
> donny@donny-lubuntu:~$ 
>
> I just want to be able to mount the filesystem again so I can copy all the 
> data off of it. What can I do?

Check your kernel message logs, and try to run

$ ls -l ~/.s3ql/local*donny*s3ql*-cache/
$ cat ~/.s3ql/local*donny*s3ql*-cache/* > /dev/null


It looks as if the file system holding your cache directory is broken.

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
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.

Reply via email to