On May 08 2015, Andy Cress <[email protected]> wrote:
> I’m using s3ql-1.17, and this pertains to Amazon S3.
>
> I configured an S3QL mount point with mkfs.s3ql and mount.s3ql on one
> system, then I did fsck.s3ql and mount.s3ql to the same bucket (same
> credentials) on a second system, but it worked and did not give me the
> ‘still mounted elsewhere’ message that I expected.
>
> What functions should I use instead to detect this case? Or should
> this work in fsck.s3ql / mount.s3ql in a later version?
What region is your bucket in?
S3QL tries to detect double mounts as best as it can, but there are
fundamental limits imposed by the storage backend. For the detection to
work reliably, the backend must guarantee either immediate get-after-put
or list-after-put consistency. The us-standard storage region, for
example, offers neither.
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.
