LVM and VxVM

failed to deactive volume group

 

failed to deactive volume group

Hello,

As part of a new project, I've inherited a rac 9i cluster and need to blow away the existing storage and re-configure the filesystems.

I'm currently attempting to deactive one of the volume groups but get the following message

'Failed to notify clvm daemon about volume group deactivation - Device busy'

That to me says I've got mounted filesystems that I need to unmount. However, looking at 'BDF' and 'mount' and /etc/fstab listings I can safely say nothing is mounted on this volume group.

For what other possible reason could it be busy? Is there some brutal way of forcing a deactivation? If it helps to know, the VG is also marked as shared.

Thanks.

Kind regards,

Mohammed.
Life is what you make it!
6 REPLIES 6
Sanjay_6
Honored Contributor

Re: failed to deactive volume group

Hi,

Have you checked if there is a swpa filesystem for this VG that is still active.

Hope this helps.

Regds
Sanjay_6
Honored Contributor

Re: failed to deactive volume group

Sorry, i meant swap
Geoff Wild
Honored Contributor

Re: failed to deactive volume group

Is the cluster up or down?

Try it both ways...

Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
Pramod_4
Trusted Contributor

Re: failed to deactive volume group

As you said it is activated in shared mode:

Is the VG activated on both nodes?

If it is shared, are there only raw LVs out there?

Did you try to deactivate it from both nodes?

Do not force shutdown the cluster at this time, that will lock up the VG in an inconsistent state and you will end up bouncing your servers!

Try the following:

Try to deactivate the VG from all the nodes.
Do a "vgchange -c n -S n VG" and then try to deactivate it.

If nothing works, examine your cluster configuration for inconsistency and bounce the server.

Pramod


Aranzazu
Frequent Advisor

Re: failed to deactive volume group

It can be because the vg is activate in a cluster mode,
Try to do this:

#vgchange -c n vgname
#vgchange -a n vgname

And remember to do after running the package that contain de vgname:

#vgchange -c y vgname

in order to avoid the fault in the cmrunpkg command.

Hope this help.

Re: failed to deactive volume group

Thanks guys,

Fortunately it was nothing complicated! Like you guys said, I tried it on the other node in the cluster and it was happy to do so (packages were still running)... I guess this was the case because of the shared attribute.

Thanks.

Kind regards,

Mohammed.
Life is what you make it!