Reboot in to the latest kernel fixed this issue. Paras. On Fri, Sep 17, 2010 at 1:19 PM, Paras pradhan <pradhanparas at gmail.com> wrote: > Hi, > My storage admin just assigned a Lun (fibre) to my server. Then re scanned using > > echo "1" > /sys/class/fc_host/host5/issue_lip > > echo "1" > /sys/class/fc_host/host6/issue_lip > > I can see the scsi device using dmesg > > But mpath device are not created for this LUN > > > Pleas see below. The last 4 should be active and I think this is the problem > > Kernel: 2.6.18-164.11.1.el5xen , EL 5.5 > -- > > [root at cvprd3 lvm]# multipathd -k > multipathd> show paths > hcil dev dev_t pri dm_st chk_st next_check > 5:0:0:0 sdb 8:16 1 [active][ready] XXX....... 7/20 > 5:0:0:1 sdc 8:32 1 [active][ready] XXX....... 7/20 > 5:0:0:16384 sdd 8:48 1 [active][ready] XXX....... 7/20 > 5:0:0:16385 sde 8:64 1 [active][ready] XXX....... 7/20 > 5:0:0:32768 sdf 8:80 1 [active][ready] XXX....... 7/20 > 5:0:0:32769 sdg 8:96 1 [active][ready] XXX....... 7/20 > 5:0:0:49152 sdh 8:112 1 [active][ready] XXX....... 7/20 > 5:0:0:49153 sdi 8:128 1 [active][ready] XXX....... 7/20 > 5:0:0:2 sdj 8:144 1 [active][ready] XXX....... 7/20 > 5:0:0:16386 sdk 8:160 1 [active][ready] XXX....... 7/20 > 5:0:0:32770 sdl 8:176 1 [active][ready] XXX....... 7/20 > 5:0:0:49154 sdm 8:192 1 [active][ready] XXX....... 7/20 > 5:0:0:3 sdn 8:208 1 [active][ready] XXX....... 7/20 > 5:0:0:16387 sdo 8:224 1 [active][ready] XXX....... 7/20 > 5:0:0:32771 sdp 8:240 1 [active][ready] XXX....... 7/20 > 5:0:0:49155 sdq 65:0 1 [active][ready] XXX....... 7/20 > 5:0:0:4 sdr 65:16 1 [active][ready] XXX....... 7/20 > 5:0:0:16388 sds 65:32 1 [active][ready] XXX....... 7/20 > 5:0:0:32772 sdt 65:48 1 [active][ready] XXX....... 7/20 > 5:0:0:49156 sdu 65:64 1 [active][ready] XXX....... 7/20 > 5:0:0:5 sdv 65:80 0 [undef] [faulty] [orphan] > 5:0:0:16389 sdw 65:96 0 [undef] [faulty] [orphan] > 5:0:0:32773 sdx 65:112 0 [undef] [faulty] [orphan] > 5:0:0:49157 sdy 65:128 0 [undef] [faulty] [orphan] > multipathd> > > Thanks in Adv > Paras. >