HP 3PAR SUSE Linux Enterprise Implementation Guide

2. Once the new LUN is visible to the QLogic driver layer, force the SCSI mid-layer to do its own

scan and build the device table entry for the new device:

# echo "scsi add-single-device 0 1 2 3" >/proc/scsi/scsi

The SCSI midlayer will re-scan, where 0 1 2 3 is replaced by your host, channel, ID, and

LUN.

Example:

# echo "scsi add-single-device 4 0 0 1" > /proc/scsi/scsi

NOTE: You must run the scsi add-single-device command individually for all the

newly discovered LUNs and on all host ports to which the LUNs were exported.

You can see the new LUN presented to the OS by the SCSI mid-Layer in the

/var/log/messages file.

kernel: qla2300 0000:03:08.0: scsi(4:0:0:1): Enabled tagged queuing, queue

depth 32.

kernel: SCSI device sdh: 14680064 512-byte hdwr sectors (7516 MB)

kernel: SCSI device sdh: drive cache: write back

kernel: sdh: sdh1

kernel: Attached scsi disk sdh at scsi4, channel 0, id 0, lun 1

kernel: Attached scsi generic sg8 at scsi4, channel 0, id 0, lun 2, type

0scsi.agent[1203]: disk at /devices/pci0000:03/0000:03:08.0/host4/target4:0:0/

4:0

Verifying Devices Found by the Host Using the QLogic HBA

To verify that the SUSE host has discovered the exported devices, look at the contents of the file

/proc/scsi/scsi. In this example, we have LUN 0 exported to the SUSE host through eight

paths (four HP 3PAR StoreServ Storage ports connecting to two QLogic HBA ports). This file should

contain entries for the attached devices:

# cat /proc/scsi/scsi

Attached devices:

Host: scsi0 Channel: 00 Id: 00 Lun: 00