- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: failed to deactive volume group
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2003 03:20 AM
тАО10-28-2003 03:20 AM
failed to deactive volume group
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2003 03:22 AM
тАО10-28-2003 03:22 AM
Re: failed to deactive volume group
Have you checked if there is a swpa filesystem for this VG that is still active.
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2003 03:22 AM
тАО10-28-2003 03:22 AM
Re: failed to deactive volume group
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2003 03:23 AM
тАО10-28-2003 03:23 AM
Re: failed to deactive volume group
Try it both ways...
Rgds...Geoff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2003 03:30 AM
тАО10-28-2003 03:30 AM
Re: failed to deactive volume group
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2003 08:02 PM
тАО10-28-2003 08:02 PM
Re: failed to deactive volume group
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2003 08:19 PM
тАО10-28-2003 08:19 PM
Re: failed to deactive volume group
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.