HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Rebuild ofRedHat defaulted to /dev/mapper/vg# ...
Operating System - Linux
1827827
Members
1979
Online
109969
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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-18-2006 05:14 AM
03-18-2006 05:14 AM
Why the /dev/mapper reference?
We were running the lastest RH ES 3 and upgraded to RedHat 4 and now when we built the volume groups it shows as /dev/mapper/yada
instead of the /dev/vg# like before.
Can this be changed back?
We were running the lastest RH ES 3 and upgraded to RedHat 4 and now when we built the volume groups it shows as /dev/mapper/yada
instead of the /dev/vg# like before.
Can this be changed back?
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2006 11:57 AM
03-18-2006 11:57 AM
Solution
Shalom,
I don't think you can change it back.
To try would be a little dicey and might lead to a loss of data.
I like the old way, because its like HP-UX.
SEP
I don't think you can change it back.
To try would be a little dicey and might lead to a loss of data.
I like the old way, because its like HP-UX.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2006 07:29 PM
03-19-2006 07:29 PM
Re: Rebuild ofRedHat defaulted to /dev/mapper/vg# ?
The new LVM system should automatically create backward-compatibility symlinks so that the old /dev/vg* paths work just as before.
It is just that tools like mount and install/update utilities prefer the "real" /dev/mapper/* paths over the symlinked /dev/vg* ones.
If you feel strongly about it, it should not be too difficult to modify the "vgscan --mknodes" command to create the traditional-style names as the real device nodes and the new ones as symlinks. This command gets executed at every boot (usually from initrd), so if you re-order the device nodes manually, the changes will not stick.
You might have to check out the udev configuration rules too: changing them might actually solve the problem just as well.
It is just that tools like mount and install/update utilities prefer the "real" /dev/mapper/* paths over the symlinked /dev/vg* ones.
If you feel strongly about it, it should not be too difficult to modify the "vgscan --mknodes" command to create the traditional-style names as the real device nodes and the new ones as symlinks. This command gets executed at every boot (usually from initrd), so if you re-order the device nodes manually, the changes will not stick.
You might have to check out the udev configuration rules too: changing them might actually solve the problem just as well.
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP