From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christophe Varoqui Subject: Re: Query: Significance of libmultipath/hwtable.c Date: Wed, 12 Jun 2013 20:15:04 +0200 Message-ID: <1371060904.30106.4.camel@lapoo.opensvc.com> References: Reply-To: christophe.varoqui@opensvc.com, device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: device-mapper development List-Id: dm-devel.ids On mer., 2013-06-12 at 11:45 +0530, amit mehta wrote: > What is the significance of libmultipath/hwtable.c file. I see there > is a list of vendors mentioned over here. > > > It's a database of defaults settings for known devices. Those settings apply when not overriden by explicit settings in multipath.conf. > grep -i vendor libmultipath/hwtable.c|uniq > .vendor = "COMPELNT", > .vendor = "APPLE*", > .vendor = "3PARdata", > .vendor = "DEC", > .vendor = "HP", > .vendor = "(COMPAQ|HP)", > .vendor = "HP", > .vendor = "DDN", > .vendor = "EMC", > .vendor = "DGC", > .vendor = "EMC", > .vendor = "FSC", > .vendor = "FUJITSU", > .vendor = "HITACHI", > .vendor = "IBM", > .vendor = "IBM", > .vendor = "AIX", > .vendor = "IBM", > .vendor = "AIX", > .vendor = "IBM", > .vendor = "AIX", > .vendor = "DELL", > .vendor = "NETAPP", > .vendor = "IBM", > .vendor = "Pillar", > .vendor = "SGI", > .vendor = "STK", > .vendor = "SUN", > .vendor = "PIVOT3", > .vendor = "SUN", > .vendor = "(LSI|ENGENIO)", > .vendor = "STK", > .vendor = "EUROLOGC", > .vendor = "NEC", > .vendor = NULL, > > > > > Under each of these vendors, there is a list of products from the same > vendor as well. So does that mean, if the vendor and or product is > not > mentioned in this file, that particular storage hardware may not be > supported by dm-multipath? > It only means that the top-level defaults settings will be applied to those multipaths. Best regards, Christophe Varoqui www.opensvc.com