Serge Victor <[email protected]> writes:
> 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:
[...]
> 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.

This is very odd. Can you try to create a file system 4 more times to
make sure it wasn't just by chance that mkfs worked but fsck
failed, and then report the issue at
https://bitbucket.org/nikratio/s3ql/issues/new?

(Please report this no matter the outcome of the repeated call, just
trying to get additional debugging information).


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