Orphaned LV ??

[Scott Frye_1]

HP-UX 11.i connected via FC to EMS CX600 SAN

We had a 10 Gig LUN from the SAN presented to our HP box. We created vg01 and lvscott. In preparation for our install of software, we needed to remove the 10 gig LUN and create several other LUNS. We removed the LUN before removing the LV or VG. Now when we try to remove the LV or VG, we can not. What would be the best way to remove this now that it is confused?

Thanks

Scott

[Pete Randall]

Scott,

Try vgexporting vg01.


Pete

[Robert-Jan Goossens_1]

Hi Scott,

Try to vgexport the volume group.

# vgexport vg01

Regards,
Robert-Jan

[Scott Frye_1]

If I do a 'vgexport vg01' it looks like "The volume group information and data is untouched on the physical volume". Would I then do a 'pvcreate -f /dev/rdsk/c?t?d?'

[Scott Frye_1]

vgexport /dev/vg01 says vg01 is active. Tried to deactivate vg01 but get a message that can not deactivate vg01, device busy.

Scott

[Borislav Perkov]

Hi,
Try to see is there any filesystem active on that LV and unmount it, or if any file is in use from the LV stop or kill the process which is running on it. Then you can deactivate the VG and remove it. If there is more than one LV in the VG than use vgreduce command, you can find useful tasks in the man pages for this command.
Regards,
Borislav

[Pete Randall · Accepted solution]

Scott,

OK, then let's try re-building the lvmtab:

mv /etc/lvmtab /etc/lvmtab.old
vgscan -a

Then check to see if /dev/vg01 exists. If it does and "strings /etc/lvmtab" shows no references to vg01, remove it:

rm -rf /dev/vg01


Pete

[Scott Frye_1]

vgscan -a worked great but it did make me nervous. Looks like others have had issues with it giving them extra data in the lvmtab file. Mine is clean...

Thanks to all!

Scott