diff options
| author |  Rajashekhara, Mahesh <Mahesh_Rajashekhara@adaptec.com>
| 2010-05-10 04:29:25 -0700 |
|---|---|---|
| committer |  James Bottomley <James.Bottomley@suse.de>
| 2010-05-16 22:58:27 -0400 |
| commit | 9cccde93fed1ca988eb2fb17ab9194bf7b5ed1b0 (patch) | |
| tree | ec928f9197c24c147ac6ac51ba981c9ca027ca77 /MAINTAINERS | |
| parent | [SCSI] aacraid: prohibit access to array container space (diff) | |
| download | linux-9cccde93fed1ca988eb2fb17ab9194bf7b5ed1b0.tar.gz linux-9cccde93fed1ca988eb2fb17ab9194bf7b5ed1b0.tar.bz2 linux-9cccde93fed1ca988eb2fb17ab9194bf7b5ed1b0.zip | |
[SCSI] aacraid: add an ifdef'd device delete case instead of taking the device offline
Problem description:
--------------------
The problem reported by one of the customer was when a logical array
is deleted(from the SDK, from the GUI, from arcconf) then the
corresponding physical device (/dev/sdb, for example) is not removed
from the Linux namespace. So you end up with a "dead" device
entry. And some of the linux tools go slightly wonky.
Solution:
---------
Based on the notification from FW, the driver calls
"scsi_remove_device" for the DELETED drive. This call not only informs
the scsi device status to the SCSI mid layer and also it will remove
corresponding scsi device entries from the Linux sysfs.
Signed-off-by: Mahesh Rajashekhara <aacraid@adaptec.com>
Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions