When issuing the command fsck, it issues the warning 'content may reappear
or content may be lost, press enter to continue' As soon as enter is
pressed it returns ERROR
Can you make any suggestions as to what could fix this?
On Monday, 31 July 2017 12:05:00 UTC+1, Andy Nottingham wrote:
>
> Hi
>
> I've inherited this s3ql link to AWS and am trying to get the file systems
> to remount after a system crash.
> Trying to mount the S3 bucket and it reports the backend reports as still
> mounted
>
> Have tried fsck.s3ql to check the file system and get the following log
>
>
> 2017-07-31 09:34:24.816 15625:MainThread
> s3ql.backends.common.get_ssl_context: Reading default CA certificates.
> 2017-07-31 09:34:24.825 15625:MainThread s3ql.backends.s3c._do_request:
> started with GET /s3ql_passphrase?None, qs=None
> 2017-07-31 09:34:24.825 15625:MainThread s3ql.backends.s3c._send_request:
> sending GET /s3ql_passphrase
> 2017-07-31 09:34:25.048 15625:MainThread s3ql.backends.s3c._do_request:
> started with GET /s3ql_passphrase?None, qs=None
> 2017-07-31 09:34:25.048 15625:MainThread s3ql.backends.s3c._send_request:
> sending GET /s3ql_passphrase
> 2017-07-31 09:34:25.192 15625:MainThread
> s3ql.backends.common.get_ssl_context: Reading default CA certificates.
> 2017-07-31 09:34:25.202 15625:MainThread s3ql.fsck.main: Starting fsck of
> s3://****-pcshares/
> 2017-07-31 09:34:25.203 15625:MainThread s3ql.backends.s3c.list: started
> with s3ql_seq_no_,
> 2017-07-31 09:34:25.203 15625:MainThread s3ql.backends.s3c.list:
> requesting with marker=
> 2017-07-31 09:34:25.203 15625:MainThread s3ql.backends.s3c._do_request:
> started with GET /?None, qs={'prefix': 's3ql_seq_no_', 'marker': '',
> 'max-keys': 1000}
> 2017-07-31 09:34:25.203 15625:MainThread s3ql.backends.s3c._send_request:
> sending GET /?prefix=s3ql_seq_no_&marker=&max-keys=1000
> 2017-07-31 09:34:25.403 15625:MainThread s3ql.backends.s3c.lookup: started
> with s3ql_seq_no_194
> 2017-07-31 09:34:25.403 15625:MainThread s3ql.backends.s3c._do_request:
> started with HEAD /s3ql_seq_no_194?None, qs=None
> 2017-07-31 09:34:25.403 15625:MainThread s3ql.backends.s3c._send_request:
> sending HEAD /s3ql_seq_no_194
> 2017-07-31 09:34:25.474 15625:MainThread s3ql.backends.s3c.lookup: started
> with s3ql_seq_no_194
> 2017-07-31 09:34:25.474 15625:MainThread s3ql.backends.s3c._do_request:
> started with HEAD /s3ql_seq_no_194?None, qs=None
> 2017-07-31 09:34:25.474 15625:MainThread s3ql.backends.s3c._send_request:
> sending HEAD /s3ql_seq_no_194
> 2017-07-31 09:34:25.508 15625:MainThread s3ql.backends.s3c.lookup: started
> with s3ql_seq_no_195
> 2017-07-31 09:34:25.508 15625:MainThread s3ql.backends.s3c._do_request:
> started with HEAD /s3ql_seq_no_195?None, qs=None
> 2017-07-31 09:34:25.508 15625:MainThread s3ql.backends.s3c._send_request:
> sending HEAD /s3ql_seq_no_195
> 2017-07-31 09:34:25.529 15625:MainThread s3ql.backends.s3c.lookup: started
> with s3ql_metadata
> 2017-07-31 09:34:25.529 15625:MainThread s3ql.backends.s3c._do_request:
> started with HEAD /s3ql_metadata?None, qs=None
> 2017-07-31 09:34:25.529 15625:MainThread s3ql.backends.s3c._send_request:
> sending HEAD /s3ql_metadata
> 2017-07-31 09:34:26.997 15625:MainThread root.excepthook:
>
> Have also tried s3ql-verify and get a similar message the file system is
> mounted elsewhere.
>
> What can I try next?
>
--
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.
