cancel
Showing results for 
Search instead for 
Did you mean: 

unable to deport: VxVM vxdg ERROR V-5-1-584 Disk group: Some volumes in the disk group are in use

IdaWong
Level 4

hi all,

i am getting this error:

VxVM vxdg ERROR V-5-1-584 Disk group : Some volumes in the disk group are in use

none of the volumes are mounted. even after vol stop all the volume in the diskgroup. it still failed to deport with the same error. any idea how to fix this without a reboot?

VRTSvxvm-5.1.132.211-5.1SP1RP2P2HF11_RHEL5 

Redhat version is 5.8

thanks inadvance.

Regards,

ida 

1 ACCEPTED SOLUTION

Accepted Solutions

Dev_Roy
Level 6
Accredited Certified

Hello Ida,


# vxprint -g <diskgroup> -m <volume> | grep devopen

If the above command returns "devopen=on" then the volume is still in an active state in the kernel, although it is probably not showing up as mounted when  the df -k command is run.

You may need to reboot the server in order to fix the issue.

 

Thanks,

Dev

View solution in original post

5 REPLIES 5

Gaurav_S
Moderator
Moderator
   VIP    Certified

Hi,

that could be a typical problem with linux ..  could u see if any process is holding the volume

# fuser /dev/vx/dsk/<diskgroup>/<volume>

if any process is holding it, you may try to kill the process & then see if dg can be deported cleanly ..

 

 

G

IdaWong
Level 4

Hi Gaurav,

Appreciate for the quick reply. unfortunately, fuser didn't report anything. some sort of lock on the volumes? 

any other idea?

 

regards,

ida 

IdaWong
Level 4

Thanks dev,

that explains it. unfortunately, i don't know enough to fix it.

according to technote

http://www.symantec.com/business/support/index?page=content&id=TECH16915

the only way is to reboot.

*sigh*

 

 

Dev_Roy
Level 6
Accredited Certified

Hello Ida,


# vxprint -g <diskgroup> -m <volume> | grep devopen

If the above command returns "devopen=on" then the volume is still in an active state in the kernel, although it is probably not showing up as mounted when  the df -k command is run.

You may need to reboot the server in order to fix the issue.

 

Thanks,

Dev

Leed_Engineer
Level 4
Partner Accredited Certified

I think in such cases with the current platform , the only way is to reboot the host.