From: Ted Ts'o <tytso@mit.edu>
To: Johann Lombardi <johann@whamcloud.com>
Cc: linux-ext4@vger.kernel.org, Andreas Dilger <adilger@whamcloud.com>
Subject: Re: [PATCH] ext4: add support for multiple mount protection
Date: Tue, 24 May 2011 17:47:14 -0400 [thread overview]
Message-ID: <20110524214714.GG26055@thunk.org> (raw)
In-Reply-To: <1305333485-17140-1-git-send-email-johann@whamcloud.com>
On Fri, May 13, 2011 at 05:38:05PM -0700, Johann Lombardi wrote:
> Prevent an ext4 filesystem from being mounted multiple times.
> A sequence number is stored on disk and is periodically updated (every 5
> seconds by default) by a mounted filesystem.
> At mount time, we now wait for s_mmp_update_interval seconds to make sure
> that the MMP sequence does not change.
> In case of failure, the nodename, bdevname and the time at which the MMP
> block was last updated is displayed.
> Move all mmp code to a dedicated file (mmp.c).
>
> Signed-off-by: Andreas Dilger <adilger@whamcloud.com>
> Signed-off-by: Johann Lombardi <johann@whamcloud.com>
Oops, I see I pulled the wrong (older) version of this patch into my
dev tree. I've corrected this and pulled in this version. Thanks!!
- Ted
next prev parent reply other threads:[~2011-05-24 21:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-14 0:38 [PATCH] ext4: add support for multiple mount protection Johann Lombardi
2011-05-24 21:47 ` Ted Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-02 8:11 MMP update Johann Lombardi
2011-05-02 9:36 ` [PATCH] ext4: add support for multiple mount protection Johann Lombardi
2011-05-23 2:19 ` Ted Ts'o
2011-04-12 18:04 Johann Lombardi
2011-04-12 19:20 ` Bernd Schubert
2011-05-02 13:43 ` Johann Lombardi
2011-04-12 20:39 ` Eric Sandeen
2011-04-12 21:08 ` Andreas Dilger
2011-04-12 21:11 ` Johann Lombardi
2011-04-12 21:41 ` Bernd Schubert
2011-04-12 21:44 ` Eric Sandeen
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=20110524214714.GG26055@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@whamcloud.com \
--cc=johann@whamcloud.com \
--cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.