From: Gionatan Danti <g.danti@assyoma.it>
To: Gionatan Danti <g.danti@assyoma.it>, linux-xfs@vger.kernel.org
Subject: Re: XFS and multiple mounts protection (aka preventing multiple mounts)
Date: Fri, 05 May 2017 15:19:45 +0200 [thread overview]
Message-ID: <c5e42df06ff981bfd6a72cbc12f10d43@assyoma.it> (raw)
In-Reply-To: <20170505122547.6gvqmdoxfaqxh3mi@eorzea.usersys.redhat.com>
Il 05-05-2017 14:25 Carlos Maiolino ha scritto:
>
> As far as I know, don't, I can always be wrong, but, I re-checked xfs
> superblock, and could not find anything that actually protects it.
>
So, how do you protect iSCSI targets from erroneous multiple mount? Do
you protect them only at the target/lun level (eg: access list on the
target/lun)?
>
> Eh, I really don't know much about EXT4, but this only works if the
> clocks are
> properly adjusted (not really hard to achieve though), but still racy.
>
I think that the mechanism tracks the relative change in the mmp
structure, rather than absolute value. Sort of "look at it, sleep,
relook, if the value changed, then does not mount"...
Thanks.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next prev parent reply other threads:[~2017-05-05 13:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 10:29 XFS and multiple mounts protection (aka preventing multiple mounts) Gionatan Danti
2017-05-05 11:32 ` Carlos Maiolino
2017-05-05 11:52 ` Gionatan Danti
2017-05-05 12:25 ` Carlos Maiolino
2017-05-05 13:19 ` Gionatan Danti [this message]
2017-05-05 16:08 ` Emmanuel Florac
2017-05-10 8:12 ` Carlos Maiolino
2017-05-10 8:19 ` Gionatan Danti
2017-05-05 19:20 ` Eric Sandeen
2017-05-08 9:34 ` Gionatan Danti
2017-05-08 13:26 ` Eric Sandeen
2017-05-08 13:36 ` Gionatan Danti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c5e42df06ff981bfd6a72cbc12f10d43@assyoma.it \
--to=g.danti@assyoma.it \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).