topic Re: LVM problem in Operating System - HP-UX

LVM problem

Duffs — Wed, 16 Jan 2008 15:48:10 GMT

Hi,

After a reboot on a rx8620 I noticed that one of our lv's can not be mounted. The disk which it belongs to appears fine in the ioscan and other lv's are mounted that also use the same disk. the lvdisplay provides the following:

--- Logical extents ---
LE PV1 PE1 Status 1
00000 ??? 00632 current
00001 ??? 00633 current
00002 ??? 00634 current
00003 ??? 00635 current
00004 ??? 00636 current
00005 ??? 00637 current
00006 ??? 00638 current
00007 /dev/dsk/c19t1d1 00000 current

I have tried vgscan and recreating the lvmtab, fsck'ing the lv, and umounting the filesystem and remounting it etc - nothing appears to be working!

R,
D.

Re: LVM problem

Steven E. Protter — Wed, 16 Jan 2008 16:02:06 GMT

Shalom,

The disk these PE's are sitting on is bad nor not present.

You need to build a new logical volume, format a filesystem if necessary and restore the files from backup.

Its possible a hot plug disk is offline. Check dmesg for that.

SEP

Re: LVM problem

Sandman! — Wed, 16 Jan 2008 16:13:06 GMT

Most likely one of the PV(s) on which that lvol resides has gone bad. Are there any lbolt or SCSI messages in the syslog? What about any EMS events in the resmon logfile? Could you attach the output of lvdisplay on that particular lvol:

# lvdisplay -v /dev/vg??/lvol??

~thanks

Re: LVM problem

Duffs — Wed, 16 Jan 2008 16:24:23 GMT

Sandman,

There are no lbolt errors in the syslog nor are there any EMS alerts in resmon.

The lvdisplay output is enclosed.

R,
D.

Re: LVM problem

Torsten. — Wed, 16 Jan 2008 16:40:17 GMT

There is something really wrong with your LUNs:

/dev/dsk/c19t1d1 12798 12798
/dev/dsk/c19t1d2 12798 12798
/dev/dsk/c19t1d3 12791 12791

add the PEs and you get
38387

But you should have
Current LE 38394
Allocated PE 38394

7 PEs are missing.

That are exactly the 7x ??? entries.

Based on this they should be on

/dev/dsk/c19t1d3

What is "pvdisplay -v" for this device is telling you?

Re: LVM problem

Duffs — Thu, 17 Jan 2008 10:04:01 GMT

Thanks for the feedback!

Issue is now resolved. I had to create a new vg and lv and reassign the fileystem to it before restoring the data to the new location.

Regards,
Duffs