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?

Using cached metadata.
Remote metadata is outdated.
Checking DB integrity...
Creating temporary extra indices...
Checking lost+found...
Checking cached objects...
Checking names (refcounts)...
Checking contents (names)...
Checking contents (inodes)...
Checking contents (parent inodes)...
Checking objects (reference counts)...
Checking objects (backend)...
..processed 43500 objects so far..object 43578 only exists in table but not 
in backend, deleting
File may lack data, moved to /lost+found: b'/Old backup/Documents and 
Settings/david/Local Settings/Application 
Data/Mozilla/Firefox/Profiles/hkwrpkxt.default/Google Gears for 
Firefox/random-domain.com/http_80/J_http_randoml-domain.com_managed[3]#localserver/38/2198500950041948929pbtplx_th0[4859].jpg'

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

-- 
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