It is just took more time then I had patience (~300 min).
I'll make a bucket copy and try patched fsck.

root@app3:/nfs/cloud/mpsrd# time fsck.s3ql --log log --debug --cachedir 
> /s3bucket/.s3cache s3://s3bucket
> Starting fsck of s3://mpsrd
> 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 205000 objects so far..
> Checking objects (sizes)...
> Checking blocks (referenced objects)...
> Checking blocks (refcounts)...
> Checking inode-block mapping (blocks)...
> Checking inode-block mapping (inodes)...
> Checking inodes (refcounts)...
> Checking inodes (sizes)...
> Checking extended attributes (names)...
> Checking extended attributes (inodes)...
> Checking symlinks (inodes)...
> Checking directory reachability...
> Checking unix conventions...
> Checking referential integrity...
> Dropping temporary indices...
> Dumping metadata...
> ..objects..
> ..blocks..
> ..inodes..
> ..inode_blocks..
> ..symlink_targets..
> ..names..
> ..contents..
> ..ext_attributes..
> Compressing and uploading metadata...
> Wrote 17 MiB of compressed metadata.
> Cycling metadata backups...
> Backing up old metadata...
> Cleaning up local metadata...
> Completed fsck of s3://mpsrd
> real    406m45.198s
> user    387m26.244s
> sys     18m6.485s

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