From: Kalpak Shah <kalpak@clusterfs.com>
To: Manoj Joseph <manoj@clusterfs.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>,
Andreas Dilger <adilger@clusterfs.com>
Subject: Re: [RFC][PATCH] Multiple mount protection
Date: Tue, 22 May 2007 13:36:16 +0530 [thread overview]
Message-ID: <1179821176.4797.15.camel@garfield> (raw)
In-Reply-To: <4652A192.9010506@clusterfs.com>
On Tue, 2007-05-22 at 13:23 +0530, Manoj Joseph wrote:
> Kalpak Shah wrote:
>
> >> Also, I am curious about this. Is there a test case for mounting the
> >> same filesystem multiple times? Does this use different paths to reach
> >> the device? Or is there a race? Or does it happen on a device shared by
> >> multiple hosts?
> >>
> >
> > If you are using some HA software, there is the possibility of a race.
> > Yes it can happen on a device shared by multiple hosts.
>
> Ah, if the HA-software doesn't deal with multiple mounts for filesystems
> it is managing, then I would claim that the software is flawed. :)
Well, it is known to happen so it wouldn't be bad to make sure.
>
> But yes, turning on MMP would help.
>
> It might also help to make the frequency at which sequence number gets
> updated (currently 5 sec) tunable. Would making that also a field in the
> super block be a bad idea (set only by mkfs/tunefs)?
Updating the MMP sequence too often would hurt the filesystem
performance.
>
> It might also be worthwhile to write the dev_t, the path of the device
> and the hostname to the s_mmp_block, along with the random sequence. (I
> assume there is enough space.) If the mount is being failed because of a
> multiple mount scenario, these fields could be used to provide useful
> diagnostics.
Yes, the dev_t, host name, the sequence and the time last updated would
all be printed. There is lots of space since we have an entire block.
> My $ 0.02. :)
Thanks. :)
>
> Regards,
> Manoj
next prev parent reply other threads:[~2007-05-22 8:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 19:52 [RFC][PATCH] Multiple mount protection Kalpak Shah
2007-05-22 7:15 ` Manoj Joseph
2007-05-22 7:34 ` Kalpak Shah
2007-05-22 7:53 ` Manoj Joseph
2007-05-22 8:06 ` Kalpak Shah [this message]
2007-05-24 23:25 ` Karel Zak
2007-05-25 6:44 ` Kalpak Shah
2007-05-25 14:39 ` Theodore Tso
2007-05-25 19:31 ` Jim Garlick
2007-05-25 21:36 ` Kalpak Shah
2007-05-30 20:58 ` Kalpak Shah
2007-05-31 16:16 ` Theodore Tso
2007-05-31 21:09 ` Kalpak Shah
2007-06-01 8:46 ` Andi Kleen
2007-06-01 8:27 ` Kalpak Shah
2007-06-01 9:14 ` Andreas Dilger
2007-06-01 10:56 ` Andi Kleen
2007-06-01 11:41 ` Theodore Tso
2007-06-01 12:13 ` Andi Kleen
2007-06-01 13:52 ` Theodore Tso
2007-06-01 18:00 ` Andreas Dilger
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=1179821176.4797.15.camel@garfield \
--to=kalpak@clusterfs.com \
--cc=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=manoj@clusterfs.com \
/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