LVM question - device files that won't go away

[Tim Killinger]

Hi - I'm practicing to hone my basic LVM skills, and I'm stumped.

I have:
- created 2 luns on a va7100
- did an ioscan -fC disk and insf -e
- did pvcreates on the resulting ctd files
- created a vg and allocated PVs,etc,etc

then to get rid of my "test" VG, I exported the vgs, blew away the ctd files and deleted the LUNS - but a subsequent ioscan and an insf -e still re-creates the ctd files. I thought that deleting the LUNS would stop the ctd files from being created... what am I missing? Thanks!!!

[Geoff Wild]

How did you delete the LUN's?

Sounds like there is still a path to the disks.

Rgds...Geoff

[James R. Ferguson]

Hi Tim:

The 'insf -e' did exactly what it should -- it created device files for devices it could see. The 'vgexport' removed the device files that belonged to the volume group -- '/dev/vgNN/group', '/dev/vgNN/lvolX' and '/dev/vgNN/rlvolX'.

Regards!

...JRF...

[Luk Vandenbussche]

Tim,

If the LUNS are well deleted, then it is certainly solved after a reboot of the server

[Rick Garland]

To avoid the reboot, can do the vgexport and this will remove the device files.

[Tim Killinger]

Geoff and all... I deleted the LUNS with CVUI interface... also if I do a vgscan -pv the device files in question are not listed... it's only when I do the insf -e that they keep reappearing (even though there are no cooresping LUNS on the VA7100 anymore)

The ctd files in question are c4t1dx and c6t1dx


icgstrn1:/home/root> vgscan -pv vgscan: The physical volume "/dev/dsk/c1t15d0" is already recorded in the "/etcvgscan: The physical volume "/dev/dsk/c4t0d1" is already recorded in the "/etc/vgscan: The physical volume "/dev/dsk/c4t0d2" is already recorded in the "/etc/vgscan: The physical volume "/dev/dsk/c4t0d3" is already recorded in the "/etc/vgscan: The physical volume "/dev/dsk/c4t0d4" is already recorded in the "/etc/vgscan: The physical volume "/dev/dsk/c4t0d5" is already recorded in the "/etc/vgscan: The physical volume "/dev/dsk/c4t0d6" is already recorded in the "/etc/vgscan: The physical volume "/dev/dsk/c4t0d7" is already recorded in the "/etc/vgscan: Physical volume "/dev/dsk/c4t1d0" is not a block special file.vgscan: Physical volume "/dev/dsk/c4t1d1" is not a block special file.vgscan: The physical volume "/dev/dsk/c6t0d1" is already recorded in the "/etc/vgscan: The physical volume "/dev/dsk/c6t0d2" is already recorded in the "/etc/vgscan: The physical volume "/dev/dsk/c6t0d3" is already recorded in the "/etc/vgscan: The physical volume "/dev/dsk/c6t0d4" is already recorded in the "/etc/vgscan: The physical volume "/dev/dsk/c6t0d5" is already recorded in the "/etc/vgscan: The physical volume "/dev/dsk/c6t0d6" is already recorded in the "/etc/vgscan: The physical volume "/dev/dsk/c6t0d7" is already recorded in the "/etc/vgscan: Physical volume "/dev/dsk/c6t1d0" is not a block special file.vgscan: Physical volume "/dev/dsk/c6t1d1" is not a block special file.Current path "/dev/dsk/c6t0d1" is an alternate link, skip.Current path "/dev/dsk/c6t0d2" is an alternate link, skip.Current path "/dev/dsk/c6t0d3" is an alternate link, skip.Current path "/dev/dsk/c6t0d4" is an alternate link, skip.Current path "/dev/dsk/c6t0d5" is an alternate link, skip.Current path "/dev/dsk/c6t0d6" is an alternate link, skip.Current path "/dev/dsk/c6t0d7" is an alternate link, skip.Couldn't stat physical volume "/dev/dsk/c2t1d0":Invalid argumentPhysical Volume "/dev/dsk/c4t0d0" contains no LVM informationCouldn't stat physical volume "/dev/dsk/c4t1d0":Invalid argumentCouldn't stat physical volume "/dev/dsk/c4t1d1":Invalid argumentPhysical Volume "/dev/dsk/c6t0d0" contains no LVM informationCouldn't stat physical volume "/dev/dsk/c6t1d0":Invalid argumentCouldn't stat physical volume "/dev/dsk/c6t1d1":Invalid argument/dev/vg00/dev/dsk/c1t15d0/dev/vgicgs/dev/dsk/c4t0d1/dev/dsk/c4t0d2/dev/dsk/c4t0d3/dev/dsk/c4t0d4/dev/dsk/c4t0d5/dev/dsk/c4t0d6/dev/dsk/c4t0d7/dev/dsk/c6t0d1/dev/dsk/c6t0d2/dev/dsk/c6t0d3/dev/dsk/c6t0d4/dev/dsk/c6t0d5/dev/dsk/c6t0d6/dev/dsk/c6t0d7icgstrn1:/home/root>

[Devender Khatana]

Hi,

The message for the above two device is clear that allthough device files are there the devices are not visible properly. How did you removed device files ?

Was it rmsf ?

These files shall go away after a system reboot if that can not be done now you shall not worry for these devices.

If these disks still consists VG information which you exported prior to removing LUNs, then vgscan will prompt you that disk with LVM information lies and use vgimport to configure them, which is not the case here.

HTH,
Devender

[Geoff Wild]

You must rmsf both the dsk and rdsk files.....or the hardware path....

Rgds...Geoff