From: Chris Mason <mason@suse.com>
To: Alexander Viro <viro@math.psu.edu>, Benjamin LaHaise <bcrl@redhat.com>
Cc: Richard Gooch <rgooch@ras.ucalgary.ca>,
Andreas Dilger <adilger@turbolabs.com>,
Doug McNaught <doug@wireboard.com>,
Lew Wolfgang <wolfgang@sweet-haven.com>,
linux-kernel@vger.kernel.org
Subject: Re: Dump corrupts ext2?
Date: Thu, 11 Oct 2001 07:47:03 -0400 [thread overview]
Message-ID: <1223310000.1002800823@tiny> (raw)
In-Reply-To: <Pine.GSO.4.21.0110110027370.21168-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0110110027370.21168-100000@weyl.math.psu.edu>
On Thursday, October 11, 2001 12:29:03 AM -0400 Alexander Viro <viro@math.psu.edu> wrote:
> On Thu, 11 Oct 2001, Benjamin LaHaise wrote:
>
>> On Wed, Oct 10, 2001 at 09:48:41PM -0400, Chris Mason wrote:
>> > The bug where dump could corrupt things was when getblk and the
>> > block device both used the buffer cache. That issue hasn't changed.
>>
>> Let me emphasize this: 2.4.11+ will still exhibit filesystem corruption if
>> the block device is accessed. The only way to avoid this is to use raw io,
>
> What? Details, please. If you are talking about read access I would
> really like to know which filesystem it is. ext2 used to have a bug
> in that area, but it had been fixed months ago.
Sorry, I wasn't very clear. As far as I know, the specific ext2 bug
(race on up to date flag of newly allocated metadata) was found/fixed
by Al.
The issues left are just dump getting inconsistent backups from
a rw mounted disk. We'll have this bug regardless of page cache vs buffer
cache vs raw io in dump.
Now, what's interesting is the raw io dump + ext3 case.
-chris
next prev parent reply other threads:[~2001-10-11 11:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 23:03 Dump corrupts ext2? Lew Wolfgang
2001-10-10 23:11 ` Doug McNaught
2001-10-10 23:34 ` Andreas Dilger
2001-10-10 23:55 ` Doug McNaught
2001-10-11 1:33 ` Richard Gooch
2001-10-11 1:48 ` Chris Mason
2001-10-11 4:16 ` Benjamin LaHaise
2001-10-11 4:29 ` Alexander Viro
2001-10-11 11:47 ` Chris Mason [this message]
2001-10-11 4:25 ` Richard Gooch
2001-10-11 2:57 ` H. Peter Anvin
2001-10-11 3:13 ` Andreas Dilger
2001-10-11 0:38 ` Mike Fedyk
2001-10-11 5:07 ` Eric W. Biederman
2001-10-10 23:28 ` H. Peter Anvin
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=1223310000.1002800823@tiny \
--to=mason@suse.com \
--cc=adilger@turbolabs.com \
--cc=bcrl@redhat.com \
--cc=doug@wireboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
--cc=viro@math.psu.edu \
--cc=wolfgang@sweet-haven.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