From: Andrey Borzenkov <arvidjaar@mail.ru>
To: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: devfs rescanning?
Date: Wed, 30 Jul 2003 23:27:25 +0400 [thread overview]
Message-ID: <200307302327.25998.arvidjaar@mail.ru> (raw)
> I have a system with 4 SCA drives. Originally they were:
>
> /dev/sda -> scsi/host0/bus0/target0/lun0/disc
> /dev/sdb -> scsi/host0/bus0/target1/lun0/disc
> /dev/sdc -> scsi/host1/bus0/target0/lun0/disc
> /dev/sdd -> scsi/host1/bus0/target1/lun0/disc
>
> SDA drive was hot-pulled to test the raid failover and it worked great.
> Next the box was rebooted after the drive was replaced (these systems
> can hang or go real stupid when a drive is pulled). The drives remapped
> as was expected. When it came back up the sd? entries had shifted up 1
> as expected
> /dev/sda -> scsi/host0/bus0/target1/lun0/disc
> /dev/sdb -> scsi/host1/bus0/target0/lun0/disc
> /dev/sdc -> scsi/host1/bus0/target1/lun0/disc
>
> and when the drive was put back in it came up as sdd. Other than a
> reboot is there any known way to get the drives back in the proper
> order? Killing devfsd, removing the entries and restarting, etc didn't
> do any good.
devfsd.conf:
REGISTER scsi/host0/bus0/target0/lun0/disc CFUNCTION GLOBAL mksymlink $devname
diska
REGISTER scsi/host0/bus0/target1/lun0/disc CFUNCTION GLOBAL mksymlink $devname
diskb
REGISTER scsi/host1/bus0/target0/lun0/disc CFUNCTION GLOBAL mksymlink $devname
diskc
REGISTER scsi/host1/bus0/target1/lun0/disc CFUNCTION GLOBAL mksymlink $devname
diskd
if you insist on calling them sda etc you may comment out MKOLDCOMPAT but
beware of consequences.
but this breaks anyway if SCSI host numbers change (e.g. if you plug in new
HBA) and for that there is no solution
-andrey
next reply other threads:[~2003-07-30 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 19:27 Andrey Borzenkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-30 15:53 devfs rescanning? Robert L. Harris
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=200307302327.25998.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=Robert.L.Harris@rdlg.net \
--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