On Fri, Aug 8, 2014 at 11:36 AM, Nikolaus Rath <[email protected]> wrote:
> Serge Victor <[email protected]> writes:
>> The s3ql worked fine. After upgrading from
>> s3ql_2.9+dfsg-2~26~ubuntu14.04.1_amd64.deb to
>> s3ql_2.10.1+dfsg-1~27~ubuntu14.04.1_amd64.deb, I am trying to upgrade
>> revision, as required, which fails:
> [...]
>> Cycling metadata backups...
>> Backing up old metadata...
>> Encountered ConnectionClosed exception (connection closed unexpectedly),
>> retrying call to Backend.copy for the 3-th time...
> [...]
>
> Are you able to create, mount, modify and umount a new filesystem using
> 2.10.1? I'd like to narrow down if the problem is specific to the
> upgrade procedure, or applies to regular usage as well.
Hi, yes, creation of the filesystem goes well, mounting goes well, but
fscking it gives the same error:
Starting fsck of swift://backupvm.random.re/blabla
[23/9569]
Using cached metadata.
File system seems clean, checking anyway.
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)...
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 154 bytes of compressed metadata.
Cycling metadata backups...
Backing up old metadata...
Encountered ConnectionClosed exception (connection closed
unexpectedly), retrying call to Backend.copy for the 3-th time...
Encountered ConnectionClosed exception (connection closed
unexpectedly), retrying call to Backend.copy for the 4-th time...
[...]
Definitely something is broken.
S.
--
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.
