On 06/16/2014 10:27 AM, PA Nilsson wrote:
> 
> 
> On Sunday, June 15, 2014 11:01:12 PM UTC+2, Nikolaus Rath wrote:
> 
>     PA Nilsson <[email protected] <javascript:>> writes:
>     > On Sunday, June 15, 2014 9:02:42 PM UTC+2, Nikolaus Rath wrote:
>     >>
>     >> On 06/15/2014 08:21 AM, PA Nilsson wrote:
>     >> > Hi,
>     >> >
>     >> > I am using a script to mount an s3ql filesystem.
>     >> > Before mounting the filesystem I am running:
>     >> >
>     >> > fsck.s3ql  --batch $storage_url
>     >> >
>     >> > If the file system was not unmounted cleanly this will fail and
>     exit.
>     >>
>     >> This should only happen if the file system was not unmounted cleanly
>     >> *and* you lost the local metadata. Otherwise it's a bug.
>     >>
>     >> If you lost the local metadata, I really don't think you want to
>     force
>     >> fsck to continue. Are you sure that's what you want?
>     >
>     > The system lost power, so the file system was not unmounted.
>     > How do I know if I have lost the local metadata?
> 
>     The fsck.s3ql message should say something about that. What message are
>     you getting when it "fails and exits"?
> 
> 
> Finally had time to reproduce this.
> The system was powercycled in the middle of running a backup with the FS
> mounted.
> Running fsck 
> 
> fsck.s3ql --ssl-ca-path ${capath} --cachedir ${s3ql_cachedir} --log
> $log_file --authfile ${auth_file}  $storage_url
> 
> "
> Starting fsck of xxxxxxxxx
> Ignoring locally cached metadata (outdated).
> 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.
> Enter "continue" to use the outdated data anyway:
> "
> 
> In this case, it is true that the file system was not cleanly unmounted,
> but what are my options here?

You should find out why you are loosing your local metadata copy.

Is your $s3ql_cachedir on a journaling file system? What happened to
this file system on the power cycle? Did it loose data?

What are the contents of $s3ql_cachedir when you run fsck.s3ql?

Are you running fsck.s3ql with the same $s3ql_cachedir as mount.s3ql?
Are you *absolutely* sure about that?


Best,
-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