public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: "Rajat  Jain, Noida" <rajatj@noida.hcltech.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Removing a disk from the qla2xxx driver.
Date: Fri, 22 Apr 2005 00:10:54 -0700	[thread overview]
Message-ID: <20050422071054.GC5069@plap.qlogic.org> (raw)
In-Reply-To: <267988DEACEC5A4D86D5FCD780313FBB0732C84F@exch-03.noida.hcltech.com>

On Wed, 20 Apr 2005, Rajat  Jain, Noida wrote:

> 
> The driver documentstion says it has the "qlascan" command which can help in
> adding new disks by the following procedure:
> 
> 1) First add the Disk to the HBA.
> 2) # echo "scsi-qlascan" > /proc/scsi/<driver-name>/<adapter-id> (The
> qla2xxx driver will rescan)

FYI:  these /proc interfaces are not present in the mainline
(upstream) qla2xxx driver.  Besides, typically these steps are only
needed if the topology isolates a LIP or SCN.  If the additional
device causes an RSCN (in the case of a fabric environment) to
propagate from the switch, the HBA will perform an SNS discovery and
login to the device.

Another alternative to forcing a LIP (and subsequently cause a
rescan), would be to initiate a bus-reset via sg_reset:

	# sg_reset -b /dev/sg0

The only downside is the /dev/sg0 device-node requirement.

> 3) # echo "scsi add-single-device 0 1 2 3" >/proc/scsi/scsi (The mid-level
> will add the device)
> 

Yes, this will instruct the mid-layer to perform its own scan.

> However, what I wanted to know was that how can I REMOVE a SCSI device from
> the HBA at run time? By logic, I believe that the sequence should be:
> 
> 1) # echo "scsi remove-single-device 0 1 2 3" >/proc/scsi/scsi (The
> mid-level will remove the device)

This is the only step that is needed.

> 2) Then remove the Disk from the HBA.
> 3) # echo "scsi-qlascan" > /proc/scsi/<driver-name>/<adapter-id> (The
> qla2xxx driver will rescan, and will remove the disk)
> 

No, the HBA's recognition of the device persists throughout the
driver's lifetime -- this is not necessary.

Hope this helps.

Regards,
Andrew Vasquez

  reply	other threads:[~2005-04-22  7:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20  5:05 Removing a disk from the qla2xxx driver Rajat  Jain, Noida
2005-04-22  7:10 ` Andrew Vasquez [this message]
2005-04-22  7:49   ` Christoph Hellwig

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=20050422071054.GC5069@plap.qlogic.org \
    --to=andrew.vasquez@qlogic.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rajatj@noida.hcltech.com \
    /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