From: "Stephen C. Tweedie" <sct@redhat.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Mike Fedyk <mfedyk@matchmail.com>,
linux-kernel@vger.kernel.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: Define conflict between ext3 and raid patches against 2.2.19
Date: Fri, 21 Sep 2001 14:10:50 +0100 [thread overview]
Message-ID: <20010921141050.A1946@redhat.com> (raw)
In-Reply-To: <20010916155835.C24067@mikef-linux.matchmail.com> <15271.11056.810538.66237@notabene.cse.unsw.edu.au> <20010919133811.B22773@mikef-linux.matchmail.com> <15273.7576.395258.345452@notabene.cse.unsw.edu.au>
In-Reply-To: <15273.7576.395258.345452@notabene.cse.unsw.edu.au>; from neilb@cse.unsw.edu.au on Thu, Sep 20, 2001 at 08:35:04AM +1000
Hi,
On Thu, Sep 20, 2001 at 08:35:04AM +1000, Neil Brown wrote:
> However when a RAID rebuild happens, every block on the array is read
> into the buffer cache (if it isn't already there) and then written
> back out again. This defeats the control that ext3 tries to maintain
> on the buffer cache.
>
> I don't know exactly what large-scale effects this might have. It
> could be simply that a crash at the wrong time could leave the
> filesystem corrupted.
Immediately after a crash, the fs will be OK. But during the
subsequent background raid reconstruction, it can get out of sync
again. This can result in silent data loss in some cases, but it is
also likely to trigger some internal ext3 debugging which detects
out-of-order data writes, resulting in a kernel panic.
Cheers,
Stephen
next prev parent reply other threads:[~2001-09-21 13:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-16 22:58 Define conflict between ext3 and raid patches against 2.2.19 Mike Fedyk
2001-09-16 23:09 ` Lehmann
2001-09-17 1:43 ` Mike Fedyk
2001-09-17 4:42 ` Andreas Dilger
2001-09-18 11:08 ` Neil Brown
2001-09-18 19:24 ` Mike Fedyk
2001-09-19 20:38 ` Mike Fedyk
2001-09-19 22:35 ` Neil Brown
2001-09-21 13:10 ` Stephen C. Tweedie [this message]
2001-09-21 22:44 ` Mike Fedyk
2001-10-01 21:17 ` Hans Reiser
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=20010921141050.A1946@redhat.com \
--to=sct@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
--cc=neilb@cse.unsw.edu.au \
/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).