lvm issues

[Mark Huff II]

I have rebboted this morning and noticed one of my filesystems did not mount "/imgData". I can see it under the file systems section in sam, but not under Logical Volumes, nor under Volume Groups.
If I try and mount "mount /dev/vg_xp_imgData/lv_xp_imgData /imgData" by hand I recieve an error "No such device or address". Although the file exists and the entry is in fstab for it.

I was going to try and create another volume group and noticed that these devices were listed as currently not being used.

How can I recreate my drive knowing which devices I need without destroying 1 terabyte of data?
I still have the file /etc/lvmconf/vg_xp_imgData.conf
Is it possible to use this file to fix this issues?

[Ted Ellis_2]

is this a new file system that was created recently.. or an old file system that has mounted on previous reboots with no problems? If it is in your fstab and all other mount points are ok.. try mount -a... what gets reported?

[Jeff Schussele · Accepted solution]

Hi Mark,

Suspect the filesystem may be dirty. But there's ways to tell.

You have to activate the VG before you can mount

vgchange -a y /dev/vg_xp_imgData

Then try to mount. If it complains it's dirty the do

fsck -o full /dev/vg_xp_imgData/rlv_xp_imgData

Note: the required use of the "raw" LV.

You should also check your /etc/rc.log file It should contain an entry if the system couldn't mount the FS because it was dirty.

Rgds,
Jeff

[Ted Ellis_2]

also.. run a vgdisplay -v on the suspect volume group and check for the logical volume in question... any errors (missing disks or LUNs)

run an ioscan and then check the status of all reported disks... any missing or not claimed...
what is the operating system and hardware in question?

[Ted Ellis_2]

you last question... you would use vgcfgrestore to restore the LVM configuration from a backup file like the one you mentioned... but follow you other checks first in verifying the issue at hand (vgdisplay, vgchange, etc.) Man page on vgcfgrestore will give you the goods on using this command.

[Anil C. Sedha]

Hi,

You may follow the following steps :

1) vgdisplay -v vg_xp_imgData

To verify if your volume group shows the entry for the logical volume.

2) lvdisplay -v /dev/vg_xp_imgData/lv_xp_imgData

Note the disk on which the filesystem is installed.

3) Do a pvdisplay for that disk

pvdisplay -v /dev/dsk/c0t0d0

4) If you find errors on these steps then run a unmount step, even though it is not officially mounted.

5) Do a fsck on the filesystem with -o option and use the raw logical volume name

6) FSCK should fix any errors with it or it will give you a message if not fixed or what the issue is.

7) If you have an additional disk you may do a pvmove of the data from one disk to another

pvmove /dev/dsk/c0t0d0(old) /dev/dsk/c1t0d0(new)

If you are still facing issues let us know.

Regards,
Anil (Don't forget to assign points if the answers are valuable to you)

[Mark Huff II]

Ted ellis...you are THE MAN!!!!!

[Mark Huff II]

Oops I meant Jeff Schussele ... You DA MAN!!!!!!!!

[Ted Ellis_2]

go Jeff!!