On 05/09/2014 05:55 AM, [email protected] wrote:
> Folks,
>
> I am using s3ql-1.17 (on CentOS5 & 6) and I have a question.
> From each system, it does fsck.s3ql to see if the bucket was previously
> formatted, and if not it does mkfs.s3ql.
This sounds dangerous. Can't you create the file system once ahead of
time? If not, why (and how) do you use fsck.s3ql for this purpose?
Wouldn't it be enough to always call mkfs.s3ql without --force?
> The issue is that if the bucket happened to be mounted on another
> system, the second one blocks forever in fsck.s3ql.
What do you mean by that? Do you mean it's waiting for input? In that
case, just redirect from /dev/null.
> Is there a way to detect that the bucket is mounted elsewhere, so I can
> avoid this?
There is no standalone program, but you should be able to just try to
mount or fsck it. If the file system is mounted elsewhere, this should
fail with an error message. Whether this is 100% reliable depends on
your backend, e.g. with Amazon S3 you are not guaranteed to always get
current data, so you can never be absolutely sure that the file system
is not mounted elsewhere.
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.
