From mboxrd@z Thu Jan 1 00:00:00 1970 From: malahal@us.ibm.com Subject: Re: boot from san & lvm Date: Mon, 7 Jan 2008 07:44:18 -0800 Message-ID: <20080107154418.GA29532@us.ibm.com> References: <64e30f320801070736o62ec8b42q9db45f616f076a17@mail.gmail.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <64e30f320801070736o62ec8b42q9db45f616f076a17@mail.gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: dm-devel@redhat.com List-Id: dm-devel.ids Urs Golla [urs.golla@gmail.com] wrote: > Hi > > I would like to boot RHEL5 from SAN. If I install with the "mpath" > parameter I can see the mapper/mpath0 device and the installation > completes without any errors. > > It boots from SAN and everything looks ok (well, lets say its > working). If i add this lines to /etc/lvm/lvm.conf > > types = [ "device-mapper", 1] > "filter = [ "a/dev/mpath/.*/", "r/.*/" ]" Try "mapper" instead of "mpath" above to handle partitions on your devices. > and remove the blacklist lines from /etc/multipath.conf as described > in the "Native Multipath Failover Based on DM-MPIO for v2.6.x Linux > Kernel and EMC(R) Storage Arrays" manual the pvscan command returns > with " No matching physical volumes found". Why? > > If I remove the filter line from lvm.conf the pvscan & pvdisplay > command returns: > > (...) > PV Name /dev/mapper/mpath0p2 > (...) > > Why is it using mpath0p2 and not mpath0? /dev/mapper/mpath0 does exist > and points to the right disks, because "multipath -ll" gives me > something like that: You must be having partitions on your disk (either you did or the installer did for you).