Red Hat Linux - hp_fibreutils/scsi_info

[James David Taylor]

When I run the utility scsi_info I only get limited information (see below)

[root@newlin1 hp_fibreutils]# scsi_info /dev/sda
SCSI_ID="0,0,0"
MODEL="COMPAQ HSV110 (C)COMPAQ"
FW_REV="3020"

It does not show the WWN nor the LUN which is the information I am looking for. How can I get this information?

[Alessandro Pilati]

What about fdisk and dmesg ?

Regards,
Alex

[James David Taylor]

I have a problem with fdisk (see below) which is why I am trying to identify the disk.

[root@newlin1 root]# fdisk /dev/sdb

Unable to read /dev/sdb

[Uwe Zessin]

> SCSI_ID="0,0,0"

Doesn't this mean: Adapter:0, Target:, LUN:0 ?


Looks like you are running Secure Path. In that case I'd use:
# spmgr display

[Alessandro Pilati]

And what about "dmesg" and "parted" ?

[James David Taylor]

Alessandro,

I have already tried dmesg but it does not give me the information I am looking for - WWLUN_ID.

parted gives me the following:-

[root@newlin1 root]# parted /dev/sdb
GNU Parted 1.6.3
Copyright (C) 1998, 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
This program is free software, covered by the GNU General Public License.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE. See the GNU General Public License for more details.

Using /dev/sdb
Error: Unable to open /dev/sdb - unrecognised disk label.
Information: The operating system thinks the geometry on /dev/sdb is 153600/64/32. Therefore, cylinder 1024 ends at 1023.999M.

This is why I am trying to identify which virtual disk it is in our EVA storage system.

[James David Taylor]

Uwe,

You are right we are using Secure Path and spmgr does indeed give me the information I require.

Thanks

[James Ruddell, CISSP]

What version of linux are you running? I'm assuming you're matching the luns on the EVA with how they're mapped in Linux?? Try vgdisplay to see if the disks (as Linux sees them) are virtual under LVM. Linux will report that the disk file systems is unknown if they are part of LVM durring boot. If the disks aren't part of LVM try dmesg | grep sd
You should see a list of all the disks from the EVA. Note that LUNS are mapped in order so LUN 1 will be /dev/sda, LUN 2 will be /dev/sdb etc.
What does your fstab look like?

[Arunvijai_4]

# /usr/sbin/lpfc/lputil
LightPulse Common Utility for Linux. Version 1.6a10 (10/7/2004).
Copyright (c) 2004, Emulex Network Systems, Inc.

Emulex Fibre Channel Host Adapters Detected: 2
Host Adapter 0 (lpfc0) is an LP9K (Ready Mode)
Host Adapter 1 (lpfc1) is an LP9K (Ready Mode)

http://www.ncsa.uiuc.edu/~aloftus/FibreChannel/Emulex/emulex.html

-Arun

[Uwe Zessin]

Sorry, but it does not work that way, because Secure Path creates a new virtual adapter and re-maps the EVA LUNs into this adapter's address space.

# spmgr display

will show you the EVA and the adapter mapping.

[James David Taylor]

James

Thanks for your input. The reason I am trying to identify the volume is because I am having problems with LVM due to a corruption in a logigal volume, which I have tried to remove, but only lead to problems (see below)

[root@newlin1 root]# pvdisplay
pvdisplay -- ERROR: VGDA in kernel and lvmtab are NOT consistent; please run vgscan

[root@newlin1 root]# man pvdisplay
[root@newlin1 root]# pvdisplay vg1
pvdisplay -- ERROR: VGDA in kernel and lvmtab are NOT consistent; please run vgscan

[root@newlin1 root]# vgdisplay
vgdisplay -- ERROR: VGDA in kernel and lvmtab are NOT consistent; please run vgscan

My real problem is how to resolve the VGDA and lvmtab inconsistency. Not sure if I have to start another thread.

[James David Taylor]

To all,

A reboot solved the inconsistency between the VGDA and lvmtab. If only the users had allowed me to do this earlier. Sigh.

Thanks for your help