- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- minor number lock
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
тАО03-24-2005 05:46 AM
тАО03-24-2005 05:46 AM
minor number lock
Created a VG and running load on that (lv was mounted).
After some time I tried to log in the lv, it failed.
vgdisplay shows that the pv status as "unavailable". But I can see that disk in securepath/autopath. Ran ioscan -fn, insf -e. No use. removed /etc/lvmtab and ran a vgscan. Now the vg was vanished from lvmtab. But still the folder was in /dev. I removed the folder and tried to create a vg with the same name. I used the same minor#. Vgcreate failed. It's complainging that the minor no is used by another vg, but actually no other VG is using the minor number. I think somewhere it was locked.
Any idea where it got locked and how to resolve this?
thanks
-Arun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-24-2005 05:51 AM
тАО03-24-2005 05:51 AM
Re: minor number lock
ll /dev/vg*/group. Check all minor numbers and user next one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-24-2005 06:38 AM
тАО03-24-2005 06:38 AM
Re: minor number lock
This kind of thing can be tricky.
I would put the old lvmtab back and vgchange -a n -q n /dev/vgWhatever.
OR
You may want to try a reboot if you can do that on this box to clear the info out of memory.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-24-2005 06:50 AM
тАО03-24-2005 06:50 AM
Re: minor number lock
We can reboot the system, but I guess that's not a right solution we can provide to customers.
Until we reboot we can't use that minor number. This also a problem.
Any idea how to break this lock and re-use the old minor number????
thanks
-Arun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-24-2005 07:55 AM
тАО03-24-2005 07:55 AM
Re: minor number lock
We're not dealing with a "normal" situation so I don't think that its a problem to ask for the reboot.
This is an "exception" where the VG has disappeared. I would agree that it should not be a "normal" thing to do.
The only other approach would be to vgchange -a y /dev/WHATEVER then vgchange -a n /dev/WHATEVER.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-24-2005 09:17 AM
тАО03-24-2005 09:17 AM