From: Roe Peterson <roe@liveglobalbid.com>
To: linux-kernel@vger.kernel.org
Subject: raid1 problems in 2.5.26 (maybe started at .1?)
Date: Mon, 22 Jul 2002 09:40:35 -0600 [thread overview]
Message-ID: <3D3C2773.F33D425@liveglobalbid.com> (raw)
I'm adding 2.5.26 to a stock redhat 7.3 distribution, which was
installed with a raid1 root
filesystem on /dev/hda1 and /dev/hdb1.
This is on a Dell GX-260 w/256MB RAM, twin 20MB IDE hard drives.
The system boots 2.5.26, runs, resyncs the raid1 array, and then, just
as the resync
finishes, the BUG at line 655 in drivers/md/raid1.c goes off:
if (waitqueue_active(&conf->wait_resume)) BUG();
There are no other raid arrays on the system.
I _seriously_ hesitate to simply comment out the bugcheck :-)
It seems that the 2.5.1 patch made wholesale changes to the raid1
subsystem...
Anyone ever seen anything like this? Have I missed something external
to the
kernel that needs to be updated between 2.4.18 and 2.5.26?
next reply other threads:[~2002-07-22 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 15:40 Roe Peterson [this message]
2002-07-22 16:03 ` raid1 problems in 2.5.26 (maybe started at .1?) kwijibo
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=3D3C2773.F33D425@liveglobalbid.com \
--to=roe@liveglobalbid.com \
--cc=linux-kernel@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