Ok. Let me go step-wise. First problem was multipath was not getting loaded at boot time, hence you had to run multipath after every boot. With the earlier suggestion, is this problem now gone? Thanks, Pradipmaya. On Jan 17, 2008 12:45 PM, Nath, Varun <varun.nath@xxxxxxx> wrote: > I am also getting these errors when I try to access those LUNs > > Jan 17 14:39:29 x kernel: device-mapper: dm-multipath: error getting > device > Jan 17 14:39:29 x kernel: device-mapper: error adding target to table > > -----Original Message----- > From: dm-devel-bounces@xxxxxxxxxx [mailto:dm-devel-bounces@xxxxxxxxxx] > On Behalf Of Nath, Varun > Sent: Thursday, January 17, 2008 2:39 PM > To: device-mapper development > Subject: RE: Need Help > > > [root@x init.d]# /etc/init.d/multipathd status > multipathd (pid 4563) is running... > [root@x init.d]# /etc/init.d/multipath status > -bash: /etc/init.d/multipath: No such file or directory > [root@x init.d]# /etc/init.d/ multipath status > -bash: /etc/init.d/: is a directory > [root@x init.d]# > > -----Original Message----- > From: dm-devel-bounces@xxxxxxxxxx [mailto:dm-devel-bounces@xxxxxxxxxx] > On Behalf Of malahal@xxxxxxxxxx > Sent: Thursday, January 17, 2008 2:36 PM > To: dm-devel@xxxxxxxxxx > Subject: Re: Need Help > > Pradipmaya Maharana [pradipmaya@xxxxxxxxx] wrote: > > Run the following: > > > > # chkconfig multipathd on > > # /etc/init.d/ multipath status > > The second command actually is "/etc/init.d/multipathd status" > to get the status of the given rc script (multipathd in this case) > > --Malahal. > > -- > dm-devel mailing list > dm-devel@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/dm-devel > > > > > > -- > dm-devel mailing list > dm-devel@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/dm-devel > > > > > > -- > dm-devel mailing list > dm-devel@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/dm-devel > -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
