Hello,
Running s3qladm upgrade seems stuck, strace on the process show something
like that
[pid 2176] write(1, "Encountered ConnectionTimedOut e"..., 123 <unfinished
> ...>
> [pid 2177] clock_gettime(CLOCK_REALTIME, {1423361411, 616936804}) = 0
> [pid 2176] <... write resumed> ) = 123
> [pid 2176] gettimeofday({1423361411, 616983}, NULL) = 0
> [pid 2176] futex(0x9fa8e4,
> FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 90516991, {1423361411,
> 621983000}, ffffffff <unfinished ...>
> [pid 2177] futex(0x9fa8e4, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x9fa8e0,
> {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
> [pid 2176] <... futex resumed> ) = 0
> [pid 2176] futex(0x9fa8a0, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
> [pid 2177] futex(0x9fa8a0, FUTEX_WAKE_PRIVATE, 1) = 1
> [pid 2176] <... futex resumed> ) = 0
> [pid 2176] futex(0x9fa8a0, FUTEX_WAKE_PRIVATE, 1) = 0
> [pid 2176] select(0, NULL, NULL, NULL, {300, 0} <unfinished ...>
> [pid 2177] write(1, "Encountered ConnectionTimedOut e"..., 123) = 123
> [pid 2177] select(0, NULL, NULL, NULL, {300, 0}
before next try.
> ubuntu@10-0-0-1:~$ time s3qladm upgrade s3://data
>
> Getting file system parameters..
>
>
>> I am about to update the file system to the newest revision.
>
> You will not be able to access the file system with any older version
>
> of S3QL after this operation.
>
>
>> You should make very sure that this command is not interrupted and
>
> that no one else tries to mount, fsck or upgrade the file system at
>
> the same time.
>
>
>>
>> Please enter "yes" to continue.
>
> > yes
>
> Downloading & uncompressing metadata...
>
> Reading metadata...
>
> ..objects..
>
> ..blocks..
>
> ..inodes..
>
> ..inode_blocks..
>
> ..symlink_targets..
>
> ..names..
>
> ..contents..
>
> ..ext_attributes..
>
> Upgrading from revision 21 to 22...
>
> ..processed 9497646/9497653 objects (100.0%, 0 bytes
>> rewritten)..Encountered ConnectionTimedOut exception (send/recv timeout
>> exceeded), retrying call to Backend.copy for the 3-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 3-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 3-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 3-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 3-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 3-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 3-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 3-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 3-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 3-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 3-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 3-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 4-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 4-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 4-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 4-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 4-th time...
>
> Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
>> retrying call to Backend.copy for the 4-th time...
>
>
>
size of metadata more then 3.5GB
I have tried with same result twice, second time on EC2 unit
Previous try I canceled on
Encountered ConnectionTimedOut exception (send/recv timeout exceeded),
> retrying call to Backend.copy for the 151-th time...
Few month ago, I had same issue with s3ql.mount. I resolve it using
following mount option:
> mount.s3ql --cachedir /data/.s3cache/ --cachesize 45000000
> --max-cache-entries 1000000 --threads 16 --allow-other --backend-options
> no-ssl,tcp-timeout=30 --nfs s3://data data
Unfortunately, s3qladm do not accept --backend-options, at least according
to help.
Please advice, upgrade process is running almost 3th day long
Not sure, but seems I could mount with 2.12 version as workaround.
Thanks,
--
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.
