On Apr 09 2015, Raz <[email protected]> wrote:
> Having some trouble with fsck... unfortunately I'm not running the latest 
> version. I'm assuming the issue relates to the file name but I cant be 
> sure... I assume its as simple as going into the cached metadata and 
> removing the file reference but can somebody confirm? If so is that as 
> trivial as opening the metadata with an sqlite management tool and ditching 
> a line in that case?
>
[...]
> 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.9', 'console_scripts', 'fsck.s3ql')()
>   File "/usr/lib64/python3.3/site-packages/s3ql/fsck.py", line 1193, in main
>     fsck.check()
>   File "/usr/lib64/python3.3/site-packages/s3ql/fsck.py", line 86, in check
>     self.check_objects_id()
>   File "/usr/lib64/python3.3/site-packages/s3ql/fsck.py", line 887, in 
> check_objects_id
>     (_, newname) = self.resolve_free(b"/lost+found", escape(path))
>   File "/usr/lib64/python3.3/site-packages/s3ql/fsck.py", line 940, in 
> resolve_free
>     name += b'-'
> TypeError: Can't convert 'bytes' object to str implicitly

Actually that's a bug in S3QL, and most likely also present in the
most-recent version. Could you please file a report at
https://bitbucket.org/nikratio/s3ql/issues?status=new&status=open? I'll
look into it as soon as I have time.

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