Hi Alessandro,
On Mon, 20 Mar 2023, at 17:15, Alessandro Boem wrote:
>>> I've changed the line to raise the NoSuchObject instead to fetch the
>>> passphrase but it return the same error.
>>> Running fsck it doesn't raise the exception at line 283 but the one at line
>>> 325 of common.py
>>> So the backend seem to gave the correct response 404 requesting a correctly
>>> missing s3ql_passphrase, but s3ql_metadata is unreadable.
>>> Do I have to try the others copy of s3ql_metadata?
>>
>> Above you said you are running `s3qladm download-metadata` and that this
>> failed. Could you please include the full command and full output of
>> everything you have done (not your summary of it)?
>
> File system was created last year with this command:
> mkfs.s3ql --plain --cachedir=/var/cache/s3ql/bdrive/
> --authfile=/etc/s3ql.authinfo s3c://r1-it.storage.cloud.it/bdrive
> We've used it till 13/03/2023. We keep mounted it on the same machine where
> we created it.
>
> This is the sequence of commands I ran and their output after the crash:
>
> root@srvorg06:~# /usr/bin/fsck.s3ql s3c://r1-it.storage.cloud.it/bdrive
> --authfile=/etc/s3ql.authinfo --cachedir=/var/cache/s3ql/bdrive/
> ERROR: File system revision needs upgrade (or backend data is corrupted)
>
> root@srvorg06:~# /usr/bin/s3qladm download-metadata
> s3c://r1-it.storage.cloud.it/bdrive --authfile=/etc/s3ql.authinfo
> --cachedir=/var/cache/s3ql/bdrive/
> ERROR: File system revision needs upgrade (or backend data is corrupted)
>
> On 18/03/2023 following this thread, I changed the command on line 265 of
> common.py from 'backend.fetch('s3ql_passphrase')' to 'raise
> NoSuchObject('s3ql_passphrase')' and I ran:
> root@srvorg06:~# /usr/bin/fsck.s3ql s3c://r1-it.storage.cloud.it/bdrive
> --authfile=/etc/s3ql.authinfo --cachedir=/var/cache/s3ql/bdrive/
> ERROR: File system revision needs upgrade (or backend data is corrupted)
This is quite intriguing. I don't understand where this exception is coming
from if not from attempting to read the s3ql_passphrase object.
Could you apply the following patch and re-run both 's3qladm download-metadata'
and 'fsck.s3ql'?
diff --git a/src/s3ql/logging.py b/src/s3ql/logging.py
index 6238fb1..ad16784 100644
--- a/src/s3ql/logging.py
+++ b/src/s3ql/logging.py
@@ -141,7 +141,7 @@ def setup_excepthook():
def excepthook(type_, val, tb):
root_logger = logging.getLogger()
- if isinstance(val, QuietError):
+ if False:
root_logger.error(val.msg)
sys.exit(val.exitcode)
else:
Best,
-Nikolaus
--
GPG 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/s3ql/80973768-79e2-4873-80c3-59e409dbd016%40app.fastmail.com.
