From: Marc MERLIN <marc_news@merlins.org>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm -A /dev/md3 fails
Date: Mon, 9 Sep 2002 00:55:59 -0700 [thread overview]
Message-ID: <20020909075559.GE3806@merlins.org> (raw)
In-Reply-To: <15740.15774.911597.853392@notabene.cse.unsw.edu.au>
On Mon, Sep 09, 2002 at 04:20:14PM +1000, Neil Brown wrote:
> That is part of the reason that I wrote mdadm. It can do the right
> thing for you.
Apparently it can, but I'm having issues with it:
My conf file says:
DEVICE /dev/scsi/host*/bus*/target*/lun*/part*
ARRAY /dev/md3 level=raid5 num-devices=7 UUID=7f69d69c:2d523219:4f3d1ea7:9b7f4057 devices=/dev/scsi/host3/bus0/target8/lun0/part1,/dev/scsi/host3/bus0/target9/lun0/part1,/dev/scsi/host3/bus0/target10/lun0/part1,/dev/scsi/host3/bus0/target11/lun0/part1,/dev/scsi/host3/bus0/target12/lun0/part1,/dev/scsi/host3/bus0/target13/lun0/part1,/dev/scsi/host3/bus0/target14/lun0/part1
gargamel:/etc/mdadm# mdadm -A -v /dev/md3
mdadm: No identity information available for /dev/md3 - cannot assemble.
Any idea why
mdadm -A -v /dev/md3 doesn't work?
Am I supposed to actually start the device with
mdadm -A -v /dev/md3 /dev/scsi/host3/bus0/target*/lun0/part1 ?
or
mdadm -A -v -u 7f69d69c:2d523219:4f3d1ea7:9b7f4057 /dev/md3 ?
(I thought mdadm would get that data from the config file)
Thanks
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key
next prev parent reply other threads:[~2002-09-09 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-09 5:48 SW Raid doesn't play nice with devfs? Marc MERLIN
2002-09-09 6:20 ` Neil Brown
2002-09-09 6:27 ` Marc MERLIN
2002-09-09 11:11 ` Neil Brown
2002-09-09 7:55 ` Marc MERLIN [this message]
2002-09-09 8:18 ` mdadm -A /dev/md3 fails Derek Vadala
2002-10-10 15:34 ` Marc MERLIN
2002-09-09 11:07 ` 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=20020909075559.GE3806@merlins.org \
--to=marc_news@merlins.org \
--cc=linux-raid@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 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.