Skip to main content

EMC PowerPath, LVM and clusters

Another note on using PowerPath in Linux...

When using 2 Linux servers and PowerPath with a bunch of shared LUNs in order to build a cluster, e.g. Oracle RAC, you have to ensure that on both servers the LUNs are designated as the same /dev/emcpower* devices. Linux is a bit flaky in device enumeration and often, the order of devices gets mixed up. PowerPath can easily fix this.
Use powermt save file=devmap.pp on one host of the cluster and use powermt unmanage dev=emcpower{a,b} and powermt load file=devmap.pp on the other, to make sure they both have the same mapping. Then do a 'powermt save' to make the configuration persistent.

Also, when using LVM in conjunction with PowerPath, you don't want regular SCSI devices (local disks or perhaps iSCSI) to intervene. You can tell LVM to ignore certain devices completely when it comes to LVM. In my case I've included the filters below to make sure Linux VMs and BMs (bare metals) get the proper config. Put this in /etc/lvm/lvm.conf

# add EMCpower devices and sdb, reject all other SCSI disks and any CDs
#BM#filter = [ "a|/dev/emcpower.*|","a|/dev/sdb|","r|/dev/sd.*|","r|/dev/cd.*|" ]
# add any SCSI devices, reject all IDE disks and CDs
#VM#filter = [ "a|/dev/sd.*|","r|/dev/hd.*|","r|/dev/cd.*|" ]

See also the CentOS docs on Controlling LVM Device Scans with Filters

Comments

Popular posts from this blog

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.

Removing VGs or LVs from LVM

While are many excellent tutorials about creating and using LVM on Linux, not may show you how you can remove disks from LVM Volume Groups (VG) and reclaim storage or how to remove a Logical Volume (LV) from your LVM set-up. Here is what I did: Use -t to TEST ANY LVM action first! We are going to release 1 TB from LVM. The Volume group was extended with 1 TB storage to serve as a cheap NFS/CIFS file server when setting up our data center. It is now deprecated and replaced by a NAS so it's no longer needed. 1) check LVM; note the four 256 GB LUNs [root@server ~]# pvscan -v Wiping cache of LVM-capable devices Wiping internal VG cache Walking through all physical volumes PV /dev/sdb1 VG vgdata lvm2 [50.00 GB / 0 free] PV /dev/sdc1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdd1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sde1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdf1 VG vgdata lvm2 [256.00 GB / 0 free] PV /dev/sdg ...

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 66254 cache hi...