linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: devfs rescanning?
Date: Wed, 30 Jul 2003 11:53:45 -0400	[thread overview]
Message-ID: <20030730155345.GK786@rdlg.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]



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.

Robert


:wq!
---------------------------------------------------------------------------
Robert L. Harris                     | GPG Key ID: E344DA3B
                                         @ x-hkp://pgp.mit.edu 
DISCLAIMER:
      These are MY OPINIONS ALONE.  I speak for no-one else.

Diagnosis: witzelsucht  	

IPv6 = robert@ipv6.rdlg.net	http://ipv6.rdlg.net
IPv4 = robert@mail.rdlg.net	http://www.rdlg.net

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-07-30 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 15:53 Robert L. Harris [this message]
2003-07-30 19:27 devfs rescanning? Andrey Borzenkov

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=20030730155345.GK786@rdlg.net \
    --to=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;
as well as URLs for NNTP newsgroup(s).