[dm-devel] Multi-Path on SuSe

christophe varoqui christophe.varoqui at free.fr
Tue Dec 14 20:01:49 UTC 2004


> 1 DL585 running SLES 9 with kernel 2.6.5-7.111.5.  Two Qlogic HBAs using
> the 8.00.00 driver. Each HBA is connected to a Fibre Channel switch
> (Total of two switches).  Each switch also has a port from the target I
> am using connected to it.  I am using HP arrays, XP128 and the XP12000,
> two ports on each arrays.  
> 
Good, this is an unreported target hardware yet.
We'll try to have it straight.

> I started the Multipathd daemon
> 
> And I get the following:
> 
> Dec 13 21:10:08 netsrv83 multipathd: --------start up-------- 
> Dec 13 21:10:08 netsrv83 multipathd: start DM events thread 
> Dec 13 21:10:08 netsrv83 multipathd: initial reconfigure multipath maps 
> Dec 13 21:10:08 netsrv83 multipathd: no devmap found 
> Dec 13 21:10:08 netsrv83 multipathd: path checkers start up 
> Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 65:160 
> Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 65:176 
> Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 65:192 
> Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 65:208 
> Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 65:224 
> Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 65:240 
> Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 66:0 
> Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 66:16 
> Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 66:32 
> Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 66:48 
> Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 66:64 
> Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 66:80 
> Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 66:96 
> Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 66:112 
> Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 66:128 
> Dec 13 21:10:08 netsrv83 multipathd: path checker startup : 66:144
>  ...................... (more the the rest of the Luns)
> 
Mostly good, but the multipath tool didn't configured any multipath
map ... we'll need to track that.

> Followed by the following after a little while:
> 
The little while is the time for the fd leak to fill the entire fd
space ... upgrade to 0.4.0

> Dec 13 21:12:40 netsrv83 multipathd: 67:64 : readsector0 checker reports
> path is down 
> Dec 13 21:12:40 netsrv83 multipathd: 67:80 : readsector0 checker reports
> path is down 
> Dec 13 21:12:40 netsrv83 multipathd: 67:96 : readsector0 checker reports
> path is down 
...

> 
> Running the command multipath -v 2 doesn't yield any output and /dev had
> no dm device created.
> 
That the heart of the problem.
You should compile the tool with DEBUG=3 and sent the output.

regards,
-- 
christophe varoqui <christophe.varoqui at free.fr>





More information about the dm-devel mailing list