[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4DA4B885.6020004@redhat.com>
Date: Tue, 12 Apr 2011 15:39:33 -0500
From: Eric Sandeen <sandeen@...hat.com>
To: Johann Lombardi <johann@...mcloud.com>
CC: linux-ext4@...r.kernel.org, Andreas Dilger <adilger@...mcloud.com>
Subject: Re: [PATCH] ext4: add support for multiple mount protection
On 4/12/11 1:04 PM, 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.
>
> Signed-off-by: Andreas Dilger <adilger@...mcloud.com>
> Signed-off-by: Johann Lombardi <johann@...mcloud.com>
> ---
> fs/ext4/ext4.h | 56 ++++++++-
> fs/ext4/super.c | 363 ++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> 2 files changed, 416 insertions(+), 3 deletions(-)
>
There was a lot of skepticism about this last time, and I imagine there still is...
400 new lines of kernel code for this, and if the other machine is hung up for 5 seconds and doesn't update, it can still be multiply-mounted anyway, right?
BUG: soft lockup - CPU#0 stuck for 10s! anyone? :(
I don't see the value in it for upstream ext4, but then hey, ext4 rarely meets a feature it doesn't like ;)
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists