VxVM problem - delete lvol

[uvc]

Hi,

I'm trying to delete a VxVM volum and have the following problem:

vxvol -g dgprod2 stop TTS_lun2
vxvm:vxvol: ERROR: Volume TTS_lun2 is currently open or mounted

I checked with fuser and lsof and nothing seems to use it. Why does this happen? What do I do?

OS: B.11.11
VxVM:
root@biprod1:/PDWH/oradata/PTRANS# swlist |grep -i vx
Base-VXVM B.03.50.5 Base VERITAS Volume Manager Bundle 3.5 for HP-UX
PHCO_26252 1.0 mount_vxfs(1M) cumulative patch
PHCO_29310 1.0 vxdump(1M) hang.
PHCO_29819 1.0 VxVM 3.5m CVM Patch for MC/SG
PHCO_29926 1.0 fsck_vxfs sync switch;invalid sparse inode
PHCO_29980 1.0 VxVM 3.5m Command Cumulative Patch 05
PHKL_28999 1.0 getmount_entry;rename;creat;[u]mount;VxFS3.5
PHKL_29045 1.0 vx_mapbad errors during fsadm -d
PHKL_29335 1.0 vx_nospace on NFS write.
PHKL_29981 1.0 VxVM 3.5m Kernel Cumulative Patch 05
PHKL_29985 1.0 VxFS perf of mmap()d files, dmapi patch
PHKL_30218 1.0 VxVM,EMC,Psets&vPar,slpq1,KRS,CDUMP,EVA,LVM

[Robert-Jan Goossens]

How about forcing it with the -f option.

# vxvol -f -g dgprod2 stop TTS_lun2

Robert-Jan

[uvc]

Well it's a prod environment and I'm afraid of doing damage... Why does this thing happen?

[Peter Nikitka]

Hi,

maybe the filesystem containing the volume is NFS-exported (look in /etc/exports)?

mfG Peter

[Bharat Katkar]

Hi,

# mount | grep vxvol TTS_lun2

Look at the directory on which this volume is mounted e.g. dir10

# umount /dir10
# vxvol -g dgprod2 stop TTS_lun2

Hope that works.
Regards,

[Dmitriy Peshiy]

Hi!

Have you tried to use vxassist -g "groupname" volume "volumename" !"diskname"?

Dmitriy.

[Ralph Grothe · Accepted solution]

If you know for sure you want to delete that volume why do you hesitate to use the -f switch?
Besides, vxvol stop ... doesn't delete the volume but only disables it.
In order to delete it you would have to run vxassist remove ..., as Dmitri suggested, or on a lower level vxplex -o rm ...
Check with vxprint the state of the volume and the used plexes below.

[Ralph Grothe]

Forgot to mention,
try disabling all subvolumes recuresively by using the -a switch in vxvol stop.

Check with a hirarchical view of the DG
(e.g. vxprint -htg )

[uvc]

Hey all,
The lvol was used as an Oracle 9i RAC tablespace (raw device mode). As far as oracle is concerned - it is not in use. But i'm reluctant because of the low possibility that this would cause oracle to fall - and maybe cause data corruption.

So this rules out the mount/nfs stuff. I'm going to try the rest of the replies.
(BTW: lsof/fuser were checked on both RAC hosts)

[Alzhy]

if you're using the VXVM volume as a RAW device - then to ensure that Oracle or any other subsystem is really using it do a :

fuser /dev/vx/rdsk/DGNAME/VOLNAME

It will give you the PID of the processe(s) that still have hooks to that device.