From: "Martin Clauss" <clauss@neuro.informatik.uni-ulm.de>
To: linux-raid@vger.kernel.org
Subject: Problems with SCSI devices renaming...
Date: Tue, 19 Oct 2004 16:47:40 +0200 [thread overview]
Message-ID: <001201c4b5ea$958f0790$30493c86@clever> (raw)
Hi all,
i got a problem with my raid. Current setup:
raiddev /dev/md/0
raid-level 5
nr-raid-disks 10
nr-spare-disks 0
persistent-superblock 1
parity-algorithm left-symmetric
device /dev/scsi/host2/bus0/target0/lun0/part1
raid-disk 0
device /dev/scsi/host2/bus0/target1/lun0/part1
raid-disk 1
device /dev/scsi/host2/bus0/target2/lun0/part1
raid-disk 2
device /dev/scsi/host2/bus0/target3/lun0/part1
raid-disk 3
device /dev/scsi/host2/bus0/target4/lun0/part1
raid-disk 4
device /dev/scsi/host2/bus0/target8/lun0/part1
raid-disk 5
device /dev/scsi/host2/bus0/target9/lun0/part1
raid-disk 6
device /dev/scsi/host2/bus0/target10/lun0/part1
raid-disk 7
device /dev/scsi/host2/bus0/target11/lun0/part1
raid-disk 8
device /dev/scsi/host2/bus0/target12/lun0/part1
raid-disk 9
This works very fine so far. But when I attach an additional device to this
DEC Storage Device, I get an additional target on this SCSI bus. Now this
doesn't matter for the devfs names, but the superblock of the RAID saves
major/minor numbers that are wrong now. So the raid won't start anymore....
Shouldn't autodetect handle exactly this problem? (Yes, partition type is
linux raid autodetect for all raid disks...)
I guess, this should be a quite common problem, so I hope to find some
answers here.
Greetz,
Martin Clauss
next reply other threads:[~2004-10-19 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 14:47 Martin Clauss [this message]
2004-10-19 15:02 ` Problems with SCSI devices renaming Luca Berra
2004-10-19 17:35 ` Martin Clauss
2004-10-19 19:38 ` Anu Matthew
2004-10-19 15:08 ` Matt Domsch
2004-10-19 15:15 ` Guy
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='001201c4b5ea$958f0790$30493c86@clever' \
--to=clauss@neuro.informatik.uni-ulm.de \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).