- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Shared Volume Group not deactivating with vgchange...
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
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
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
05-26-2016 09:27 AM
05-26-2016 09:27 AM
Shared Volume Group not deactivating with vgchange -a n <vg>
2 node Service Guard Cluster with a shared Volume group/logical volume, with Oracle 11g RAC. De-actiavtion of the Shared Logical volume group use to work (vgchange -a n <vg>).
Now after Oracle is shutdown with "crsctl stop has", and all the oracle processes are dead, (ps -ef shows no oracle user on the box) the vg cannot be deactivated (vgchange -a n <vg>). It complains about a lock cannot be stopped - /etc/lvmconf/pv_lock is still open (was up till 430 am trying to get it to work) or something of the sorts.....Is there some way to find what process has the shared logical volume still open?
If the node is shutdown it panics the system because the os will not release the lock on the shared VG. IN MY CASE, a LV RESYNC of the same VG/LV we are trying to close, on the opposite node was occuring at the same time. Will this prevent the Shared volume group/LV on the Opposite node from deactivating or would I have something else holding the LV lock?
We are running the Sept.15 of the Quality Pack patches on the nodes.