From: spam@streefland.xs4all.nl (Dick Streefland)
To: linux-kernel@vger.kernel.org
Subject: Re: md wierdness with 2.6.0test9
Date: Sat, 01 Nov 2003 13:41:29 -0000 [thread overview]
Message-ID: <281b.3fa3b808.d7ab2@altium.nl> (raw)
In-Reply-To: 1067654148.19557.409.camel@up
Brad Langhorst <brad@langhorst.com> wrote:
| array syncs up but i see this wierdness (it exists across reboots)
| from mdadm --details /dev/md0
|
| Number Major Minor RaidDevice State
| 0 22 1 0 active sync /dev/hdc1
| 1 0 0 -1 removed
| 2 3 1 1 spare /dev/hda1
|
| rebooting to a 2.4 series kernel appears to fix this problem...
Mmm, this looks familiar to me. See my email to linux-raid:
http://www.spinics.net/lists/raid/msg03610.html
The patch in one of the replies fixed the problem for me.
However, this patch hasn't been included in Linus' kernel yet.
--
Dick Streefland //// De Bilt
dick.streefland@xs4all.nl (@ @) The Netherlands
------------------------------oOO--(_)--OOo------------------
prev parent reply other threads:[~2003-11-01 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 2:35 md wierdness with 2.6.0test9 Brad Langhorst
2003-11-01 13:41 ` Dick Streefland [this message]
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=281b.3fa3b808.d7ab2@altium.nl \
--to=spam@streefland.xs4all.nl \
--cc=dick.streefland@xs4all.nl \
--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