Nikolaus - as always, thank you for you prompt reply. I will try increasing the timeout as a workaround and report the "issue' to Softlayer for them to investigate. Thanks again.
-Kevin On Monday, April 4, 2016 at 2:06:25 AM UTC-5, Kevin Grace wrote: > > S3QL filesystem dismounted on its own. When trying to remount, got error > saying to rerun FSCK. Running FSCK results in the following error > everytime. We have uploaded quiet a bit of data and wondering if we're > hitting a size/object limit,etc. Here's the command and resulting error > (in red below)....this goes on until it times out then dies. Any > assistance is appreciated very much. > > root@rs:~# fsck.s3ql swift:// > sjc01.objectstorage.service.networklayer.com/rs_container > Starting fsck of swift:// > sjc01.objectstorage.service.networklayer.com/rs_container/ > 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 12645147 objects so far.. > Checking objects (sizes)... > Checking blocks (referenced objects)... > Checking blocks (refcounts)... > Checking blocks (checksums)... > 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 753 MiB of compressed metadata. > Cycling metadata backups... > Backing up old metadata... > Encountered ConnectionTimedOut exception (send/recv timeout exceeded), > retrying call to Backend._copy_helper for the 3-th time... > Encountered ConnectionTimedOut exception (send/recv timeout exceeded), > retrying call to Backend._copy_helper for the 4-th time... > Encountered ConnectionTimedOut exception (send/recv timeout exceeded), > retrying call to Backend._copy_helper for the 5-th time... > Encountered ConnectionTimedOut exception (send/recv timeout exceeded), > retrying call to Backend._copy_helper for the 6-th time... > Encountered ConnectionTimedOut exception (send/recv timeout exceeded), > retrying call to Backend._copy_helper for the 7-th time... > Encountered ConnectionTimedOut exception (send/recv timeout exceeded), > retrying call to Backend._copy_helper for the 8-th time... > Encountered ConnectionTimedOut exception (send/recv timeout exceeded), > retrying call to Backend._copy_helper for the 9-th time... > > -- 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.
