HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: multipath map VS lvm2 map
Operating System - Linux
1829106
Members
2505
Online
109986
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
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
11-12-2010 08:31 AM
11-12-2010 08:31 AM
multipath map VS lvm2 map
Hi All
Having issue in linux with lvm kicking in before multipath.
since lvm is depending on the volumes setup in /dev/mapper by multipath
and if lvm cannot find any, the multipath volumes are not used by lvm. so i have written a shell to do all the work manually on startup.
please let me know a way to fix this issue.
thank you
Having issue in linux with lvm kicking in before multipath.
since lvm is depending on the volumes setup in /dev/mapper by multipath
and if lvm cannot find any, the multipath volumes are not used by lvm. so i have written a shell to do all the work manually on startup.
please let me know a way to fix this issue.
thank you
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2010 08:53 AM
11-12-2010 08:53 AM
Re: multipath map VS lvm2 map
Welcome to ITRC Forums!
The LVM configuration file /etc/lvm/lvm.conf contains some settings that can prevent this issue.
All versions of LVM2 support the "filter" keyword, which can be used to make LVM use only multipathed devices.
Newer versions (about RHEL 4.5 and above, I think) also have the "preferred_names" keyword, which can be used to make LVM favor multipath devices over non-multipath devices. If the "preferred_names" keyword is supported in your Linux distribution, the lvm.conf file usually contains a commented-out example line for exactly this purpose:
-----
preferred_names = [ ]
# Try to avoid using undescriptive /dev/dm-N names, if present.
# preferred_names = [ "^/dev/mpath/", "^/dev/mapper/", "^/dev/[hs]d" ]
-----
If your lvm.conf includes lines like this, just comment out the first preferred_names line, and uncomment the second one.
The lvm.conf file is a readable text file, and it usually contains a lot of commented-out examples for the most important keywords. There is also a man page: type "man lvm.conf" to read it.
(If you're using multipathed disks and your lvm.conf does not support the preferred_names keyword, your system is rather old. You should seriously consider upgrading to the latest update level: after the preferred_names keyword was added, many other important updates to both LVM an dm-multipath have been released, so you would be likely to get other reliability improvements too.)
MK
The LVM configuration file /etc/lvm/lvm.conf contains some settings that can prevent this issue.
All versions of LVM2 support the "filter" keyword, which can be used to make LVM use only multipathed devices.
Newer versions (about RHEL 4.5 and above, I think) also have the "preferred_names" keyword, which can be used to make LVM favor multipath devices over non-multipath devices. If the "preferred_names" keyword is supported in your Linux distribution, the lvm.conf file usually contains a commented-out example line for exactly this purpose:
-----
preferred_names = [ ]
# Try to avoid using undescriptive /dev/dm-N names, if present.
# preferred_names = [ "^/dev/mpath/", "^/dev/mapper/", "^/dev/[hs]d" ]
-----
If your lvm.conf includes lines like this, just comment out the first preferred_names line, and uncomment the second one.
The lvm.conf file is a readable text file, and it usually contains a lot of commented-out examples for the most important keywords. There is also a man page: type "man lvm.conf" to read it.
(If you're using multipathed disks and your lvm.conf does not support the preferred_names keyword, your system is rather old. You should seriously consider upgrading to the latest update level: after the preferred_names keyword was added, many other important updates to both LVM an dm-multipath have been released, so you would be likely to get other reliability improvements too.)
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2010 10:12 AM
11-12-2010 10:12 AM
Re: multipath map VS lvm2 map
Hi Matti
Thank you.
The contents of /dev/mapper for multipath devices are as follows
data-part1 (LVM partition of data)
wal-part1 (LVM partition of wal)
indices-part1 (LVM partition of indices)
Note: data, wal and indices are the volumes mapped from MSA to linux using friendly names,
and in lvm.conf
under devices section ...
devices {
dir = "/dev"
scan = [ "/dev" ]
preferred_names = [ ]
filter = [ "a/mapper/", "r/.*/" ]
cache_dir = "/etc/lvm/cache"
cache_file_prefix = ""
write_cache_state = 1
types = [ "device-mapper", 254 ]
sysfs_scan = 1
md_component_detection = 1
ignore_suspended_devices = 0
}
and this does not work.
so i will have to change the preferred_names to
preferred_names = [ "^/dev/mapper/" ]
these are the only active settings, other settings are commented out.
thanks.
Thank you.
The contents of /dev/mapper for multipath devices are as follows
data-part1 (LVM partition of data)
wal-part1 (LVM partition of wal)
indices-part1 (LVM partition of indices)
Note: data, wal and indices are the volumes mapped from MSA to linux using friendly names,
and in lvm.conf
under devices section ...
devices {
dir = "/dev"
scan = [ "/dev" ]
preferred_names = [ ]
filter = [ "a/mapper/", "r/.*/" ]
cache_dir = "/etc/lvm/cache"
cache_file_prefix = ""
write_cache_state = 1
types = [ "device-mapper", 254 ]
sysfs_scan = 1
md_component_detection = 1
ignore_suspended_devices = 0
}
and this does not work.
so i will have to change the preferred_names to
preferred_names = [ "^/dev/mapper/" ]
these are the only active settings, other settings are commented out.
thanks.
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP