<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Multipath on</title><link>https://geekyschmidt.com/tags/multipath/</link><description>Recent content in Multipath on</description><generator>Hugo -- 0.160.1</generator><language>en</language><copyright>Copyright © 2002–2025, Nicholas Schmidt; all rights reserved.</copyright><lastBuildDate>Mon, 15 Sep 2008 10:30:51 +0000</lastBuildDate><atom:link href="https://geekyschmidt.com/tags/multipath/index.xml" rel="self" type="application/rss+xml"/><item><title>Multipath and Redhat Linux 5</title><link>https://geekyschmidt.com/2008/09/15/multipath-and-redhat-linux-5/</link><pubDate>Mon, 15 Sep 2008 10:30:51 +0000</pubDate><guid>https://geekyschmidt.com/2008/09/15/multipath-and-redhat-linux-5/</guid><description>&lt;p&gt;As many of you know, multipath was finally integrated into Redhat Linux with the 5 series. This is great when you have multipath enabled during an install as you will see /dev/mapper/mpath0, but what happens post install when you attach new LUN? Here is the howto for what happens behind the scenes during a RHEL install:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;After the filer has attached and presented the new LUN reboot the machine allowing for the HBA card to recognize them&lt;/li&gt;
&lt;li&gt;Post-reboot login and verify with the drivers are present with the correct capacity: &lt;em&gt;dmesg | grep sd&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Next we need the WWID for the new path. For this example assume that sdh is one of our newly presented multipath drives: &lt;em&gt;scsi_id -gus /block/sdh&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Copy this output down and have it ready to input into a config file. I recommend pipping or copying down the results withing GNOME/vim&lt;/li&gt;
&lt;li&gt;Edit the /etc/multipath.conf with your editor of choice and look for the blacklist exception list. You will see a WWID “923847089123908u2389” already listed. Copy that line and replace the “218934708912374” with the output of command #3&lt;/li&gt;
&lt;li&gt;Reboot the box&lt;/li&gt;
&lt;li&gt;After the reboot login and cd /dev/mapper and verify that there is a newly listed mpath1. If this is not the case stop what you are doing and wash-rinse-repeat steps 1-6&lt;/li&gt;
&lt;li&gt;If there is a mpath1 we need to create a new partition. Since Linux sees the device as a new block, use fdisk as you would with any other drive: &lt;em&gt;fdisk /dev/mapper/mpath1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Since the drive is freshly paritioned you will need to reboot to allow the kernel to recognize the new parition table.&lt;/li&gt;
&lt;li&gt;Post reboot we can create a filesystem. I am going to assume you created one parition and are going to use ext3: &lt;em&gt;mkfs.ext3 /dev/mapper/mpath1p1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Next edit your /etc/fstab and point the new drive to a path you want the new mapping mounted to: &lt;em&gt;/dev/mapper/mpath1p1 /storage ext3 defaults 1 1&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;For the next portion I will operate under the assumption you are attaching more storage to your /opt directory for a new commercial install. As root drop to run level 2: &lt;em&gt;init 2&lt;/em&gt; This is the lowest run level where the / filesystem is mounted r/w and multipathd is running&lt;/li&gt;
&lt;li&gt;We will move /opt as it is current substatianted to /opt2: &lt;em&gt;mv /opt /opt2&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Create the mount for the SAN LUN: &lt;em&gt;mkdir /opt&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;Mount the LUN: &lt;em&gt;mount /opt&lt;/em&gt; &amp;lt;–read from the /etc/fstab entry&lt;/li&gt;
&lt;li&gt;Now we sync the directories with rsync: &lt;em&gt;rsync -avh /opt2/* /opt&lt;/em&gt; I recommend holding onto the /opt2 until everything is tested after a reboot&lt;/li&gt;
&lt;li&gt;Done!&lt;/li&gt;
&lt;/ol&gt;</description></item><item><title>filter = [ &amp;#8220;a/sda[1-9]$/&amp;#8221; &amp;#8220;a/e&amp;#8230;</title><link>https://geekyschmidt.com/2007/06/18/filter-asda1-9-ae/</link><pubDate>Mon, 18 Jun 2007 05:59:47 +0000</pubDate><guid>https://geekyschmidt.com/2007/06/18/filter-asda1-9-ae/</guid><description>&lt;p&gt;filter = [ “a/sda[1-9]$/” “a/emcpower.*/” “r/.*/” ] This fixes problems with EMC PowerPath and LVM&lt;/p&gt;</description></item></channel></rss>