From: Robert Murray <rob@mur.org.uk>
To: linux-kernel@vger.kernel.org
Subject: raid1 oops in 2.6.9 (debian package 2.6.9-1-686-smp)
Date: Sun, 28 Nov 2004 14:28:41 +0000 [thread overview]
Message-ID: <20041128142840.GA4119@mur.org.uk> (raw)
Hi
The complete console log can be found at http://haylott.plus.com/~robbie/md-oops.txt
hde is a failed drive. In this log, hdg (the other drive in the raid1
array) is not present. This oops also occurs when hdg is present. I
don't know why it tries to use hde when it has been failed for some
time now. This doesn't occur with 2.6.8 (also a debian kernel). I
don't have a log of the oops when hdg was present, but I can provide
one if necessary.
Please let me know if there is any other information I can provide to
help to debug this. For now I have removed hde and everything is
working fine.
Best regards
Rob
next reply other threads:[~2004-11-28 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 14:28 Robert Murray [this message]
2004-11-29 10:07 ` raid1 oops in 2.6.9 (debian package 2.6.9-1-686-smp) Jakob Oestergaard
2004-11-29 12:02 ` Jurriaan
2004-11-29 12:51 ` Jakob Oestergaard
2004-11-30 1:58 ` Neil Brown
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=20041128142840.GA4119@mur.org.uk \
--to=rob@mur.org.uk \
--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