Can't deal with logical volume

[Tamer Shaalan]

Hiii ALL,

I have created a logical volume in a volume group that contains my application and assigned a file system to it. I have made full recovery to the machine from the application recovery tape (Installing HP-UX first and applying application recovery). Application recovery creates the volume group of the application. the problem is that this logical volume now is not working (0 size , Unused). when I try to delete it, I have :

# lvremove /dev/nfmdg/Storage
lvremove: Couldn't delete logical volume "/dev/nfmdg/Storage":
The supplied lv number refers to a non-existent logical volume.
Volume Group configuration for /dev/nfmdg has been saved in /etc/lvmconf/nfmdg.conf

and when I try to create a logical volume with the same name, it gives me there is already a logical volume with the same name.

what can I do to deal with this LV?

Thanks in advance.

Tamer.

[Tamer Shaalan]

When I tried to create a file system for this logical volume

# newfs -F vxfs /dev/nfmdg/rStorage
vxfs newfs: Cannot open /dev/nfmdg/rStorage: No such device or address

# cd /dev/nfmdg
#ll
.
.
.
brw-r----- 1 root sys 64 0x010017 Dec 1 19:53 OracleVol_snap
brw-r----- 1 root sys 64 0x010003 Dec 1 19:52 OrbixVol
brw-r----- 1 root sys 64 0x010018 Dec 1 19:53 OrbixVol_snap
brw-r----- 1 root sys 64 0x010009 Dec 1 19:52 PUVol
brw-r----- 1 root sys 64 0x010019 Dec 1 19:53 PUVol_snap
brw-r----- 1 root sys 64 0x01001b Nov 25 14:30 Storage
brw-r----- 1 root sys 64 0x010007 Dec 1 19:52 TabVol
brw-r----- 1 root sys 64 0x01001a Dec 1 19:53 TabVol_snap
crw-r----- 1 root sys 64 0x010018 Dec 1 19:53 rOrbixVol_snap
crw-r----- 1 root sys 64 0x010009 Dec 1 19:52 rPUVol
crw-r----- 1 root sys 64 0x010019 Dec 1 19:53 rPUVol_snap
crw-r----- 1 root sys 64 0x01001b Nov 25 14:30 rStorage
crw-r----- 1 root sys 64 0x010007 Dec 1 19:52 rTabVol
crw-r----- 1 root sys 64 0x01001a Dec 1 19:53 rTabVol_snap

what about the modification date of these files of LV. the machine restored at 1st of Dec.

Tamer

[Cheryl Griffin]

Are you trying to remove them or restore them?
How many lvols does vgdisplay show:
# vgdisplay /dev/nfmdg
...
Max LV 255
Cur LV 10
Open LV 10
...

Maybe the volume group thinks these lvols no longer exist but they were restored from the archive.

If this is the case, remove the device files and use lvcreate so that the LVM structure is updated.

[Tamer Shaalan]

Dear Cheryl,

Thanks for your reply

vgdisplay gives :

LV Name /dev/nfmdg/Storage
LV Status available/syncd
LV Size (Mbytes) 0
Current LE 0
Allocated PE 0
Used PV 0

I thinked really to remove deive files for this logical volume, and I alraedy created one with the same name but different size, this has solved the problem.

Tamer

[Tamer Shaalan]

The solution is found and written in my reply