From: Paul Slootman <paul+nospam@wurtel.net>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: md: bug in file drivers/md/md.c, line 1513
Date: Thu, 24 Mar 2005 10:07:19 +0100 [thread overview]
Message-ID: <20050324090719.GA11613@wurtel.net> (raw)
In-Reply-To: <16961.60764.827542.318291@cse.unsw.edu.au>
On Thu 24 Mar 2005, Neil Brown wrote:
> On Tuesday March 22, paul+nospam@wurtel.net wrote:
> > This is on kernel 2.6.11, mdadm 1.4.0
> >
> > The system has MD devices that are auto-configured on boot.
> >
> > However, there are also devices connected via another SCSI adapter
> > (actually, a Qlogic QLA2300). I'm using a module for that. As the
> > auto-configure only runs at boot (or rather, when the md subsystem is
> > started). I wanted to restart a raid-0 device that I had previously
> > created. I did:
> >
> > mdadm --run /dev/md10
>
> As you admit, this is wrong. You want something like
> mdadm --assemble /dev/md10 /dev/.....(list of component devices)
>
> or describe the md10 array (e.g. via UUID) in /etc/mdadm.conf
It took a bit of trial and error (I find the mdadm docs a bit
confusing...) but I came up with this:
mdadm --assemble --super-minor=10 --config=partitions /dev/md10
> > error message in the subject, and a "COMPLETE RAID STATE PRINTOUT"...
> > In that output there is a line "md10:", the next line is
> > "md1: <sde1><sdd1><sdc1><sdb1><sda1>".
> >
> >
> > Admittedly the usage may be wrong, but having the kernel say "bug" can't
> > be right :-)
> >
>
> Yes, there are quite a few of those silly bug messages. I've removed
> a few, but have not yet gone through and checked and removed all the
> bad ones.
Keep up the good work :-)
Paul Slootman
prev parent reply other threads:[~2005-03-24 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 16:44 md: bug in file drivers/md/md.c, line 1513 Paul Slootman
2005-03-23 22:27 ` Neil Brown
2005-03-24 9:07 ` Paul Slootman [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=20050324090719.GA11613@wurtel.net \
--to=paul+nospam@wurtel.net \
--cc=linux-kernel@vger.kernel.org \
--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