Missing LVM disks, kind of

[Mitchell Johnston]

I am having a problem with LVM when trying to add logical volume. I thought it was an issue with /etc/lvmtab. I tried to recreate it, but it did not work. Any help?

See the attached document for deatils.

[Pedro Cirne]

Hi,

What LVM errors are you having? Would you post the errors?

Pedro

[melvyn burnard]

what errors or messages did you get when issung the lvcreate command?

[S.Arunkumar]

Hi Mitchell
It seems no problem with the lvmtab file.Can u post the error message what you get during the lvcreate and in which VG

Regards
S.Arunkumar

[Kent Ostby]

Mitchell --

It looks like there is a descrepency on the second vg since it shows 4 Current and 3 Active PVs.

I know you have six physical devices in lvmtab for it. I think these are two links of three devices each. Did you have a fourth drive or initially do an add of a device before it was a link ?

[Mitchell Johnston]

The error I get when adding a volume:

The command used to create logical volumes, /sbin/lvcreate, has
failed. The stderr output from the command is shown below. The
logical volume has not been created.

vgcfgbackup: /etc/lvmtab is out of date with the running
kernel:Kernel indicates 7 disks for "/dev/lawvg1"; /etc/lvmtab has 6
disks.
Cannot proceed with backup.

Help

[Pedro Cirne]

Hi,

The vg display shows that current PV=4 and active PV=3.

Check with ioscan -fnCdisk if "/dev/dsk/c0t6d0" is CLAIMED.

Did you add/remove disk from this server? Are those this on a SAN?

Pedro

[S.Arunkumar · Accepted solution]

Hey

Can u activate the Vg in low quorum mode.

#vgchange -a y -q n /dev/vglaw1


Regards
S.Arunkumar

[Mitchell Johnston]

No disk changes have been made. It is using an EMC and that is not showing any errors. Nor have any changes been made.

[Mitchell Johnston]

This worked:

ustpdev4[/]#vgchange -a y -q n /dev/lawvg1
Volume group "/dev/lawvg1" has been successfully changed.

[S.Arunkumar]

Hi Mitchell

Whether you can able to create the LV now.In that case I request you to reboot your system once then your problem will get shorted out for ever.

One more thing You can appreciate the efforts made by this team by providing points to them

Regards
S.Arunkumar

[Pedro Cirne]

Hi,

Probably c6t0d0/c8t0d0 are the "gatekeepers" of the EMC storage:

Please post the output of:

diskinfo /dev/rdsk/c6t0d0
diskinfo /dev/rdsk/c8t0d0
diskinfo /dev/rdsk/c6t0d3
diskinfo /dev/rdsk/c0t6d0

Also check if /dev/dsk/c0t6d0 is CLAIMED when you do ioscan -fnCdisk

Thks

Pedro

[Mitchell Johnston]

I will post the points. Here is the output:

ustpdev4[/]#vgchange -a y -q n /dev/lawvg1
Volume group "/dev/lawvg1" has been successfully changed.
ustpdev4[/]#ioscan -fnCdisk
Class I H/W Path Driver S/W State H/W Type Description
====================================================================================
disk 0 0/0/1/0.6.0 sdisk CLAIMED DEVICE HP
DVD-ROM 305
/dev/dsk/c0t6d0 /dev/rdsk/c0t6d0
disk 1 0/0/2/0.6.0 sdisk CLAIMED DEVICE SEAGATE
ST336704LC
/dev/dsk/c1t6d0 /dev/rdsk/c1t6d0
disk 2 0/0/2/1.6.0 sdisk CLAIMED DEVICE SEAGATE
ST336704LC
/dev/dsk/c2t6d0 /dev/rdsk/c2t6d0
disk 3 0/4/0/0.33.35.19.0.0.0 sdisk CLAIMED DEVICE EMC
SYMMETRIX
/dev/dsk/c6t0d0 /dev/rdsk/c6t0d0
disk 17 0/4/0/0.33.35.19.0.0.3 sdisk CLAIMED DEVICE EMC
SYMMETRIX
/dev/dsk/c6t0d3 /dev/rdsk/c6t0d3
disk 18 0/4/0/0.33.35.19.0.1.1 sdisk CLAIMED DEVICE EMC
SYMMETRIX
/dev/dsk/c6t1d1 /dev/rdsk/c6t1d1
disk 19 0/4/0/0.33.35.19.0.1.2 sdisk CLAIMED DEVICE EMC
SYMMETRIX
/dev/dsk/c6t1d2 /dev/rdsk/c6t1d2
disk 11 0/4/0/0.33.35.19.0.3.1 sdisk CLAIMED DEVICE EMC
SYMMETRIX
/dev/dsk/c6t3d1 /dev/rdsk/c6t3d1
disk 12 0/4/0/0.33.35.19.0.3.2 sdisk CLAIMED DEVICE EMC
SYMMETRIX
/dev/dsk/c6t3d2 /dev/rdsk/c6t3d2
disk 13 0/4/0/0.33.35.19.0.3.3 sdisk CLAIMED DEVICE EMC
SYMMETRIX
/dev/dsk/c6t3d3 /dev/rdsk/c6t3d3
disk 7 1/12/0/0.33.31.19.0.0.0 sdisk CLAIMED DEVICE EMC
SYMMETRIX
/dev/dsk/c8t0d0 /dev/rdsk/c8t0d0
disk 20 1/12/0/0.33.31.19.0.0.3 sdisk CLAIMED DEVICE EMC
SYMMETRIX
/dev/dsk/c8t0d3 /dev/rdsk/c8t0d3
disk 21 1/12/0/0.33.31.19.0.1.1 sdisk CLAIMED DEVICE EMC
SYMMETRIX
/dev/dsk/c8t1d1 /dev/rdsk/c8t1d1
disk 22 1/12/0/0.33.31.19.0.1.2 sdisk CLAIMED DEVICE EMC
SYMMETRIX
/dev/dsk/c8t1d2 /dev/rdsk/c8t1d2
disk 14 1/12/0/0.33.31.19.0.3.1 sdisk CLAIMED DEVICE EMC
SYMMETRIX
/dev/dsk/c8t3d1 /dev/rdsk/c8t3d1
disk 15 1/12/0/0.33.31.19.0.3.2 sdisk CLAIMED DEVICE EMC
SYMMETRIX
/dev/dsk/c8t3d2 /dev/rdsk/c8t3d2
disk 16 1/12/0/0.33.31.19.0.3.3 sdisk CLAIMED DEVICE EMC
SYMMETRIX
/dev/dsk/c8t3d3 /dev/rdsk/c8t3d3
ustpdev4[/]#diskinfo /dev/rdsk/c6t0d0
SCSI describe of /dev/rdsk/c6t0d0:
vendor: EMC
product id: SYMMETRIX
type: direct access
size: 7680 Kbytes
bytes per sector: 512
ustpdev4[/]#diskinfo /dev/rdsk/c8t0d0
SCSI describe of /dev/rdsk/c8t0d0:
vendor: EMC
product id: SYMMETRIX
type: direct access
size: 7680 Kbytes
bytes per sector: 512
ustpdev4[/]#diskinfo /dev/rdsk/c6t0d3
SCSI describe of /dev/rdsk/c6t0d3:
vendor: EMC
product id: SYMMETRIX
type: direct access
size: 48602880 Kbytes
bytes per sector: 512
ustpdev4[/]#diskinfo /dev/rdsk/c0t6d0
SCSI describe of /dev/rdsk/c0t6d0:
vendor: HP
product id: DVD-ROM 305
type: CD-ROM
size: 0 Kbytes
bytes per sector: 0

[Pedro Cirne]

Hi,

I was right, c6t0d0/c8t0d0 are EMC "gatekeepers".

Try vgscan again, but with the flag -a

vgscan -v -a

I know that there are some issues when using vgscan on EMC storages, I'v had some problems in the past.

Pedro

[Mitchell Johnston]

Result
ustpdev4[/]#vgscan -v -a
Creating "/etc/lvmtab".
Couldn't stat physical volume "/dev/dsk/c0t6d0":
Invalid argument
Physical Volume "/dev/dsk/c6t0d0" contains no LVM information
Physical Volume "/dev/dsk/c8t0d0" contains no LVM information


/dev/vg00
/dev/dsk/c1t6d0
/dev/dsk/c2t6d0



/dev/lawvg1
/dev/dsk/c6t0d3
/dev/dsk/c6t1d1
/dev/dsk/c6t1d2
/dev/dsk/c8t0d3
/dev/dsk/c8t1d1
/dev/dsk/c8t1d2



/dev/testvg
/dev/dsk/c6t3d1
/dev/dsk/c6t3d2
/dev/dsk/c6t3d3
/dev/dsk/c8t3d1
/dev/dsk/c8t3d2
/dev/dsk/c8t3d3


Scan of Physical Volumes Complete.
*** LVMTAB has been created successfully.
*** If PV links are configured in the system.
*** Do the following to resync information on disk.
*** #1. vgchange -a y
*** #2. lvlnboot -R

[Pedro Cirne]

Hi,

I suppose vgcfgbackup still gives you an error..

Post the output of the attached cmpdisks.dat script

Pedro

[Mitchell Johnston]

Scanning host ustpdev4 .......................

***** LVM-VG: 0602389353-1023904892
1 ustpdev4:c6t3d1 0602389353-1023904886 0/4/0/0.33.35.19.0.3.1 EMC/SYMMETRIX (0x02/testvg/0602389353-1023904892)
ustpdev4:c8t3d1 0602389353-1023904886 1/12/0/0.33.31.19.0.3.1 EMC/SYMMETRIX (0x02/testvg/0602389353-1023904892)
2 ustpdev4:c6t3d2 0602389353-1023904888 0/4/0/0.33.35.19.0.3.2 EMC/SYMMETRIX (0x02/testvg/0602389353-1023904892)
ustpdev4:c8t3d2 0602389353-1023904888 1/12/0/0.33.31.19.0.3.2 EMC/SYMMETRIX (0x02/testvg/0602389353-1023904892)
3 ustpdev4:c6t3d3 0602389353-1023904889 0/4/0/0.33.35.19.0.3.3 EMC/SYMMETRIX (0x02/testvg/0602389353-1023904892)
ustpdev4:c8t3d3 0602389353-1023904889 1/12/0/0.33.31.19.0.3.3 EMC/SYMMETRIX (0x02/testvg/0602389353-1023904892)

***** LVM-VG: 0657389353-1012569560
1 ustpdev4:c1t6d0 0657389353-1012569560 0/0/2/0.6.0 SEAGATE/ST336704LC (0x00/vg00/0657389353-1012569560)
2 ustpdev4:c2t6d0 0657389353-1014211828 0/0/2/1.6.0 SEAGATE/ST336704LC (0x00/vg00/0657389353-1012569560)

***** LVM-VG: 0657389353-1032208149
1 ustpdev4:c6t1d1 0657389353-1032208145 0/4/0/0.33.35.19.0.1.1 EMC/SYMMETRIX (0x03/lawvg1/0657389353-1032208149)
ustpdev4:c8t1d1 0657389353-1032208145 1/12/0/0.33.31.19.0.1.1 EMC/SYMMETRIX (0x03/lawvg1/0657389353-1032208149)
2 ustpdev4:c6t1d2 0657389353-1032208147 0/4/0/0.33.35.19.0.1.2 EMC/SYMMETRIX (0x03/lawvg1/0657389353-1032208149)
ustpdev4:c8t1d2 0657389353-1032208147 1/12/0/0.33.31.19.0.1.2 EMC/SYMMETRIX (0x03/lawvg1/0657389353-1032208149)
3 ustpdev4:c6t0d3 0657389353-1122459557 0/4/0/0.33.35.19.0.0.3 EMC/SYMMETRIX (0x03/lawvg1/0657389353-1032208149)
ustpdev4:c8t0d3 0657389353-1122459557 1/12/0/0.33.31.19.0.0.3 EMC/SYMMETRIX (0x03/lawvg1/0657389353-1032208149)

***** XXX: NOVOLUME
1 ustpdev4:c6t0d0 unknown 0/4/0/0.33.35.19.0.0.0 EMC/SYMMETRIX
ustpdev4:c8t0d0 unknown 1/12/0/0.33.31.19.0.0.0 EMC/SYMMETRIX

***** XXX: UNCLAIMED
1 ustpdev4:c6t4d2 unknown ??? unknown/unknown
ustpdev4:c6t4d3 unknown ??? unknown/unknown
ustpdev4:c6t4d4 unknown ??? unknown/unknown
ustpdev4:c8t4d2 unknown ??? unknown/unknown
ustpdev4:c8t4d3 unknown ??? unknown/unknown
ustpdev4:c8t4d4 unknown ??? unknown/unknown

***** XXX: ZEROSIZE
1 ustpdev4:c0t6d0 unknown 0/0/1/0.6.0 HP/DVD-ROM 305

[Mitchell Johnston]

The final solution was to deactivate the vg, export it, and dlete related device files. The do a remake of the /etc/lvmtab file and reboot. I then created a new vg with a different name and created all of the lv's that I had in the group.

I am now restoring data.

Thank you all for your help.