search for: multipathd

Hi, WARNING: Long post ahead I have an issue when starting multipathd. The kernel complains about "blk_cloned_rq_check_limits: over max segments limit". The server in question is configured for KVM hosting. It boots via iBFT to an iSCSI volume. Target is COMSTAR and underlying that is a ZFS volume (100GB). The server also has two infiniband cards providing...

...2) kernel: gnbd1: shutting down socket kernel: exiting GNBD_DO_IT ioctl kernel: gnbd1: Attempted send on closed socket gnbd_recvd[3357]: ERROR [gnbd_recvd.c:292] login refused by the server : No such device gnbd_recvd[3357]: reconnecting kernel: device-mapper: multipath: Failing path 252:1. multipathd: gnbd1: directio checker reports path is down multipathd: checker failed path 252:1 in map mpath0 multipathd: mpath0: remaining active paths: 1 gnbd_recvd[3357]: ERROR [gnbd_recvd.c:292] login refused by the server : No such device gnbd_recvd[3357]: reconnecting Now the copy process is fre...

...features "0" hardware_handler "1 rdac" prio "rdac" failback immediate rr_weight "uniform" no_path_retry "12" } } In CentOS 6.x when you restart multipathd or restart server, using multipathd -k multipathd> show config multipathd> exit in output you see your particular configuration instead than the default one for this particular device. In CentOS 7.3 instead I see it two times, the first one with the default built-in values (eg "no_path...

Hi all. While playing with iSCSI Enterprise Target + multipathd on CentOS 5.1 (both the target and the initiator/multipath/xen box are Cent 5.1), I encountered a strange fault condition that leads to a kernel panic in a version of Xen 3.2.1-rc2 pulled from a couple of days ago. My lab consists of two Clovertown machines with dual GigE into separate switches....

...rything, the one package you miss is the one that stops the update. :-( >-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of John R Pierce >Sent: 04 February 2015 19:01 >To: centos at centos.org >Subject: Re: [CentOS] multipathd > >On 2/4/2015 6:02 AM, Rushton Martin wrote: >> OS is CentOS 5.3 (yes, I know - upgrade) > >at least patch CentOS 5. 5.3 is a snapshot from 6 years ago (2009), >there've been 6 years of updates to CentOS 5 since that point, both >security and bug fixes. `yum update`...

...rything, the one package you miss is the one that stops the update. :-( >-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of John R Pierce >Sent: 04 February 2015 19:01 >To: centos at centos.org >Subject: Re: [CentOS] multipathd > >On 2/4/2015 6:02 AM, Rushton Martin wrote: >> OS is CentOS 5.3 (yes, I know - upgrade) > >at least patch CentOS 5. 5.3 is a snapshot from 6 years ago (2009), >there've been 6 years of updates to CentOS 5 since that point, both >security and bug fixes. `yum update`...

...rything, the one package you miss is the one that stops the update. :-( >-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of John R Pierce >Sent: 04 February 2015 19:01 >To: centos at centos.org >Subject: Re: [CentOS] multipathd > >On 2/4/2015 6:02 AM, Rushton Martin wrote: >> OS is CentOS 5.3 (yes, I know - upgrade) > >at least patch CentOS 5. 5.3 is a snapshot from 6 years ago (2009), >there've been 6 years of updates to CentOS 5 since that point, both >security and bug fixes. `yum update`...

...rything, the one package you miss is the one that stops the update. :-( >-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of John R Pierce >Sent: 04 February 2015 19:01 >To: centos at centos.org >Subject: Re: [CentOS] multipathd > >On 2/4/2015 6:02 AM, Rushton Martin wrote: >> OS is CentOS 5.3 (yes, I know - upgrade) > >at least patch CentOS 5. 5.3 is a snapshot from 6 years ago (2009), >there've been 6 years of updates to CentOS 5 since that point, both >security and bug fixes. `yum update`...

...rything, the one package you miss is the one that stops the update. :-( >-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of John R Pierce >Sent: 04 February 2015 19:01 >To: centos at centos.org >Subject: Re: [CentOS] multipathd > >On 2/4/2015 6:02 AM, Rushton Martin wrote: >> OS is CentOS 5.3 (yes, I know - upgrade) > >at least patch CentOS 5. 5.3 is a snapshot from 6 years ago (2009), >there've been 6 years of updates to CentOS 5 since that point, both >security and bug fixes. `yum update`...

...rything, the one package you miss is the one that stops the update. :-( >-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of John R Pierce >Sent: 04 February 2015 19:01 >To: centos at centos.org >Subject: Re: [CentOS] multipathd > >On 2/4/2015 6:02 AM, Rushton Martin wrote: >> OS is CentOS 5.3 (yes, I know - upgrade) > >at least patch CentOS 5. 5.3 is a snapshot from 6 years ago (2009), >there've been 6 years of updates to CentOS 5 since that point, both >security and bug fixes. `yum update`...

...sue_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]...

>-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of Alexander Dalloz >Sent: 04 February 2015 22:44 >To: CentOS mailing list >Subject: Re: [CentOS] multipathd > >Am 04.02.2015 um 15:02 schrieb Rushton Martin: >> Our cluster was supplied with two IBM DS3400 RAID arrays connected >> with fibre channel. Both are old and one is failing so we bought an >> IBM >> V3700 to replace it. The V3700 complained that we were using the &...

>-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of Alexander Dalloz >Sent: 04 February 2015 22:44 >To: CentOS mailing list >Subject: Re: [CentOS] multipathd > >Am 04.02.2015 um 15:02 schrieb Rushton Martin: >> Our cluster was supplied with two IBM DS3400 RAID arrays connected >> with fibre channel. Both are old and one is failing so we bought an >> IBM >> V3700 to replace it. The V3700 complained that we were using the &...

>-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of Alexander Dalloz >Sent: 04 February 2015 22:44 >To: CentOS mailing list >Subject: Re: [CentOS] multipathd > >Am 04.02.2015 um 15:02 schrieb Rushton Martin: >> Our cluster was supplied with two IBM DS3400 RAID arrays connected >> with fibre channel. Both are old and one is failing so we bought an >> IBM >> V3700 to replace it. The V3700 complained that we were using the &...

>-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of Alexander Dalloz >Sent: 04 February 2015 22:44 >To: CentOS mailing list >Subject: Re: [CentOS] multipathd > >Am 04.02.2015 um 15:02 schrieb Rushton Martin: >> Our cluster was supplied with two IBM DS3400 RAID arrays connected >> with fibre channel. Both are old and one is failing so we bought an >> IBM >> V3700 to replace it. The V3700 complained that we were using the &...

>-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of Alexander Dalloz >Sent: 04 February 2015 22:44 >To: CentOS mailing list >Subject: Re: [CentOS] multipathd > >Am 04.02.2015 um 15:02 schrieb Rushton Martin: >> Our cluster was supplied with two IBM DS3400 RAID arrays connected >> with fibre channel. Both are old and one is failing so we bought an >> IBM >> V3700 to replace it. The V3700 complained that we were using the &...

>-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of Alexander Dalloz >Sent: 04 February 2015 22:44 >To: CentOS mailing list >Subject: Re: [CentOS] multipathd > >Am 04.02.2015 um 15:02 schrieb Rushton Martin: >> Our cluster was supplied with two IBM DS3400 RAID arrays connected >> with fibre channel. Both are old and one is failing so we bought an >> IBM >> V3700 to replace it. The V3700 complained that we were using the &...

Our cluster was supplied with two IBM DS3400 RAID arrays connected with fibre channel. Both are old and one is failing so we bought an IBM V3700 to replace it. The V3700 complained that we were using the IBM's RDAC driver (true) and we were advised to change to using Linux multipath. I've done that but the default configuration for the DS3400s is: device { vendor

On 2/4/2015 6:02 AM, Rushton Martin wrote: > OS is CentOS 5.3 (yes, I know - upgrade) at least patch CentOS 5. 5.3 is a snapshot from 6 years ago (2009), there've been 6 years of updates to CentOS 5 since that point, both security and bug fixes. `yum update` would bring you up to CentOS the .11 update plus security/bug fixes since. -- john r pierce

Am 04.02.2015 um 15:02 schrieb Rushton Martin: > Our cluster was supplied with two IBM DS3400 RAID arrays connected with > fibre channel. Both are old and one is failing so we bought an IBM > V3700 to replace it. The V3700 complained that we were using the IBM's > RDAC driver (true) and we were advised to change to using Linux > multipath. I've done that but the default