From: Andreas Dilger <adilger@clusterfs.com>
To: Alex Tomas <alex@clusterfs.com>
Cc: Andrew Morton <akpm@osdl.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Fengguang Wu <fengguang.wu@gmail.com>
Subject: Re: Fw: [BUG -mm] ext3_orphan_add() accessing corrupted list on a corrupted ext3fs
Date: Thu, 1 Feb 2007 18:19:38 -0700 [thread overview]
Message-ID: <20070202011938.GC5717@schatzie.adilger.int> (raw)
In-Reply-To: <m3odod4wju.fsf@bzzz.home.net>
On Feb 01, 2007 20:28 +0300, Alex Tomas wrote:
> >>>>> Andreas Dilger (AD) writes:
> AD> I don't have a comment on the actual bug here, but this is another case
> AD> where it would be nice to have multi-mount protection built into ext3...
> AD> When I last proposed this it was refused on the grounds that an external
> AD> HA manager should be doing this job but I don't think that is realistic.
>
> can we use JBD-like approach? export some inode and MMP/whatever
> would 'ping' 1st block of the inode.
I'd be happy enough to implement the engine for this in a generic kernel
layer instead of being ext3-specific. That said, ext3 also has the
ability to mark the filesystem incompatible to older kernels that do not
support the MMP protocol, so this avoids the requirement that both
kernels are up-to-date in order to not corrupt shared images.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2007-02-02 1:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 9:08 Fw: [BUG -mm] ext3_orphan_add() accessing corrupted list on a corrupted ext3fs Andrew Morton
2007-02-01 10:25 ` Andreas Dilger
2007-02-01 17:28 ` Alex Tomas
2007-02-02 1:19 ` Andreas Dilger [this message]
2007-02-01 16:58 ` Eric Sandeen
2007-02-01 20:56 ` ext3_forget() and ext3_free_blocks() Mingming Cao
2007-02-02 10:30 ` Andreas Gruenbacher
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=20070202011938.GC5717@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--cc=alex@clusterfs.com \
--cc=fengguang.wu@gmail.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 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).