From: Marc MERLIN <marc_news@merlins.org>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: SW Raid doesn't play nice with devfs?
Date: Sun, 8 Sep 2002 23:27:37 -0700 [thread overview]
Message-ID: <20020909062737.GA3806@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:
> Yep, raidstart is broken by design. It depends on device number being
> stable, and SCSI device number aren't, especially if they are added
> after boot time.
>
> That is part of the reason that I wrote mdadm. It can do the right
> thing for you.
>
> http://www.cse.unsw.edu.au/~neilb/source/mdadm/
I will try this, thanks (I can't reboot the system this exact minute)
That said, the problem occurs both with the kernel autorun and raidstart:
when I load the qla1280 module, the drives get detected, md wakes up and
tries to create md3 since the partitions have type 0xfd, and fails in the
same way:
(...)
kernel: /dev/scsi/host3/bus0/target13/lun0: p1
kernel: SCSI device sdl: 354600001 512-byte hdwr sectors
kernel: /dev/scsi/host3/bus0/target14/lun0: p1
kernel: [events: 00000002]
kernel: md: could not lock sdm1, zero-size? Marking faulty.
(...)
Is the kernel autorun code going to be fixed too or will I need to use mdadm
for the forseable future?
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 6:27 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 [this message]
2002-09-09 11:11 ` Neil Brown
2002-09-09 7:55 ` mdadm -A /dev/md3 fails Marc MERLIN
2002-09-09 8:18 ` 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=20020909062737.GA3806@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).