can't deactivate VG

[Erol KAHRAMAN]

hi,
i have SG on two nodes. I get the following error when exec the cmhaltnode command:

root@vtnode1#cmhaltnode -f -v vtnode1
Disabling package switching to all nodes being halted.
Disabling all packages from running on vtnode1.
Warning: Do not modify or enable packages until the halt operation is completed.

Halting cluster services on node vtnode1.
Unable to halt the LVM daemon on vtnode1.
Clustered Volume Groups must be deactivated before the cluster can be halted.
Check the syslog file for more detailed information.

My syslog file give me the error mesage as below:
Jan 29 09:11:27 vtnode1 CM-CMD[24773]: cmhaltnode -f -v vtnode1
Jan 29 09:11:27 vtnode1 inetd[24774]: hacl-cfg/tcp: Connection from localhost (127.0.0.1) at Tue Jan 29 09:11:27 2008
Jan 29 09:11:27 vtnode1 inetd[24775]: ident/tcp: Connection from localhost (127.0.0.1) at Tue Jan 29 09:11:27 2008
Jan 29 09:11:27 vtnode1 cmcld: Request from root on node vtnode1 to halt the cluster on this node
Jan 29 09:11:27 vtnode1 cmcld: Request from node vtnode1 to disable switching for package vt2pkg on a node where the package isn't configured (vtnode1)
Jan 29 09:11:27 vtnode1 cmcld: Unable to disable package vt2pkg on an unconfigured node.
Jan 29 09:11:27 vtnode1 cmlvmd[4992]: Volume group vgsmlog is still active.

And when i try to change status of my VG the output error is

root@vtnode1#vgchange -a n vgsmlog
vgchange: Failed to notify clvm daemon about volume group deactivation - Device busy
Couldn't deactivate volume group "vgsmlog":
Device busy

What could be the problem? How i can deactivate may VG ?

[Steven E. Protter · Accepted solution]

Shalom,

You should be able to deactivate a volume group, even if there is a bunch of active logical volumes.

At this point, I'd recommend booting the system if possible.

Configure serviceguard not to start.

SEP

[Mridul Shrivastava]

Have you checked that there are no filesystem mounted using the LVs of this VG??

Try unmounting them first then deactivate the VG?

If there are users accessing those mount points then use fuser to identify them and if required use -k option to kill those sessions.

[Mridul Shrivastava]

you have assigned points to 10 of 28 responses. Please spare sometime from your busy schedule to assign points to all of those who spent their time to answer ur query.

Don't they deserve some reward in form of points for the time/research they have done to answer??

[Rita C Workman]

You have node vtnode1, with package vt2pkg, that has a volume group vgsmlog.
Volume group vgsmlog is still showing active and will not umount. OK...

You may be able to avoid a reboot. I will assume you have some mounts down and this vgsmlog is all that is left up. Go and find what is holding those mountpoints and kill them.
fuser -cu /

Once everything is released that is holding the mountpoints, then umount.

Then you need to change control of the volume group from the cluster and to you....
vgchange -c n /dev/vgsmlog

...and I like to activate and then de-activate...
vgchange -a y /dev/vgsmlog
vgchange -a n /dev/vgsmlog

Now do what you want....and remember when you want to put it back into the cluster...
vgchange -a n /dev/vgsmlog
vgchange -c y /dev/vgsmlog

Rgrds,
Rita

[Erol KAHRAMAN]

I can't find any way to deactivate my VG. So i restart my server. And now i can halt and run my vtnode1 node in cluster.But i really couldn't understand what is the problem.
Thanks all.