On Jul 31 2017, Andy Nottingham <[email protected]> wrote:
6> This is the console output, it just posts ERROR without any more detail.
>
>
> [root@server ~]# fsck.s3ql --debug --force --cachedir /store/.s3ql
> s3://****-pcshares
> Starting fsck of s3://dnae-dr-fs-pcshares/
> Backend reports that file system is still mounted elsewhere. Either
> the file system has not been unmounted cleanly or the data has not yet
> propagated through the backend. In the later case, waiting for a while
> should fix the problem, in the former case you should try to run fsck
> on the computer where the file system has been mounted most recently.
> You may also continue and use whatever metadata is available in the
> backend. However, in that case YOU MAY LOOSE ALL DATA THAT HAS BEEN
> UPLOADED OR MODIFIED SINCE THE LAST SUCCESSFULL METADATA UPLOAD.
> Moreover, files and directories that you have deleted since then MAY
> REAPPEAR WITH SOME OF THEIR CONTENT LOST.
> Enter "continue, I know what I am doing" to use the outdated data anyway:
>
>> ERROR:
I don't think this is actually what's happening. fsck.s3ql is waiting
for input from you here, there is no condition where it would print
"ERROR: " and abort.
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].
For more options, visit https://groups.google.com/d/optout.
