From: "Jon Hedlund" <JH_ML@invtools.com>
To: sct@redhat.com, akpm@zip.com.au
Cc: linux-kernel@vger.kernel.org
Subject: 2.2 kernel - Ext3 & Raid patches
Date: Tue, 21 May 2002 16:40:06 -0500 [thread overview]
Message-ID: <3CEA7866.23557.390B7FFC@localhost> (raw)
Last September Stephan told someone on the linux-kernel list that
Ext3 and Raid 1 didn't work together on the 2.2 kernel.
Has this been fixed or have I just been lucky? I've been using ext3
on a Raid 1 array of two IBM 75GB ide drives with kernel 2.2.19.
Three times in the last 9 months one of the drives reported errors
and dropped offline, each time I have fdisked the bad drive,
formatted it, fsck'ed it and found no problems, fdisked it again, and
raidhotadd'ed it back in and it restored the array without problems.
Two questions:
1. Besides the faulty drive, is my data in danger from this software
configuration and I've just been lucky or would this configuration not
trigger the problems Stephan was warning about?
2. What is the "proper" fix for the patch collision between the raid
patch and the ext3 patch in /include/linux/fs.h? I've just been
changing the line
#define BH_LowPrio 8
to
#define BH_LowPrio 5
around line 198, it's been working but I don't know enough about the
code to know if that might mess something else up or not work
under some conditions.
Thanks,
JonH
next reply other threads:[~2002-05-21 21:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 21:40 Jon Hedlund [this message]
2002-05-22 1:21 ` 2.2 kernel - Ext3 & Raid patches Andreas Dilger
2002-05-22 10:16 ` Stephen C. Tweedie
2002-05-23 1:11 ` Mike Fedyk
2002-05-23 7:02 ` Tomas Szepe
2002-05-23 7:03 ` David S. Miller
2002-05-23 7:21 ` Tomas Szepe
2002-05-23 8:42 ` Tomas Szepe
2002-05-23 8:49 ` Stephen C. Tweedie
2002-05-23 14:52 ` Herman Oosthuysen
2002-05-23 22:25 ` Stephen C. Tweedie
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=3CEA7866.23557.390B7FFC@localhost \
--to=jh_ml@invtools.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.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 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.