Skip to main content

Linux Device-Mapper Resource Page


Device mapper (dm) is the native Linux tool to create enterprise grade multipath and fail-over devices with that utilize SAN storage and other modern storage features from within Linux. The Device-mapper Resource Page is a good starting point.
As we're using Dell hardware (poweredge 2950), I found the white paper on using dm for multipath I/O rather helpful. It lists some basic knowledge and concepts, for those not familiar with SAN, HBA cards and other devices.
Interestingly, it also mentions that device mapper only became native to Linux with kernel 2.6.13 and backports have been ported to RHEL 4 update 2 as well as SLES 9 SP2. That makes me wonder whether device mapper is included standard in RHEL 4.4, or OEL 4U5 in our case...? Does a backport mean that you can safely add it to your existing installation if it older than update 2? And is it included by standard in any later version or update, or not?

Comments

Popular posts from this blog

Tuning the nscd name cache daemon

I've been playing a bit with the nscd now and want to share some tips related to tuning the nscd.conf file. To see how the DNS cache is doing, use nscd -g. nscd configuration: 0 server debug level 26m 57s server runtime 5 current number of threads 32 maximum number of threads 0 number of times clients had to wait yes paranoia mode enabled 3600 restart internal passwd cache: no cache is enabled [other zero output removed] group cache: no cache is enabled [other zero output removed] hosts cache: yes cache is enabled yes cache is persistent yes cache is shared 211 suggested size <==== 216064 total data pool size 1144 used data pool size 3600 seconds time to live for positive entries <==== 20 seconds time to live for negative entries

Preventing PuTTY timeouts

Just found a great tip to prevent timeouts of PuTTY sessions. I'm fine with timeouts by the host, but in our case the firewall kills sessions after 30 minutes of inactivity... When using PuTTY to ssh to your Linux/Unix servers, be sure to use the feature to send NULL packets to prevent a timeout. I've set it to once every 900 seconds, i.e. 15 minutes... See screenshot on the right.

Setting up SR-IOV in RHEL6 on PowerEdge servers

Dell Community : "RHEL 6 provides SR-IOV functionality on supported hardware which provides near native performance for virtualized guests. Single-Root I/O Virtualization (SR-IOV) specification, introduced by PCI-SIG details how a single PCIe device can be shared between various virtualization guests. Devices capable of SR-IOV functionality support multiple virtual functions on top of the physical function. Virtual Function is enabled in hardware as a light weight PCIe function. Operating System cannot discover this function as it does not respond to the PCI bus scan and requires support in the host’s driver. As in PCIe pass-through, a Virtual function of a SR-IOV capable card can be directly assigned to the guest operating system. A virtual function driver running in the guest manages this device."