* Question regarding failback option in multipath.conf
@ 2009-09-30 16:41 Eli Klein
2009-09-30 18:51 ` Eli Klein
2009-09-30 19:07 ` John Brier
0 siblings, 2 replies; 11+ messages in thread
From: Eli Klein @ 2009-09-30 16:41 UTC (permalink / raw)
To: dm-devel
[-- Attachment #1.1: Type: text/plain, Size: 2925 bytes --]
I'm running into an issue where the failback option in multipath.conf
is being ignored. I've tried to set this to a value > 0 to cause dm
to pause before reinstating a recovered path, but it reinstates the
path immediately. The same is true when setting the value to
"manual", the path is reinstated immediately. The delay is most
useful when a ethernet switch has failed or rebooted. During the boot
of the switch, the interface comes up and drops again multiple times.
I'd love to be able to introduce a delay before DM marks the path as
reinstated after a recovery. This would save me the hassle of running
into I/O errors (and occasional filesystem RO) as the path bounces
while the switch is booting.
Thanks in advance for any help or suggestions!
-Eli
I've included my multipath.conf as well as output from multipath -ll
below:
multipath.conf:
blacklist {
devnode "sda$"
# devnode "*"
}
## By default, devices with vendor = "IBM" and product = "S/390.*" are
## blacklisted. To enable mulitpathing on these devies, uncomment the
## following lines.
#blacklist_exceptions {
# device {
# vendor "IBM"
# product "S/390.*"
# }
#}
## Use user friendly names, instead of using WWIDs as names.
defaults {
user_friendly_names yes
}
##
## Here is an example of how to configure some standard options.
##
#
defaults {
udev_dir /dev
polling_interval 10
selector "round-robin 0"
path_grouping_policy multibus
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
prio_callout /bin/true
path_checker readsector0
rr_min_io 10
rr_weight priorities
failback 120
features "1 queue_if_no_path"
no_path_retry 1
user_friendly_name yes
}
multipath -ll:
mpath2 (36000eb3945b8703a00000000000000f4) dm-3 LEFTHAND,iSCSIDisk
[size=400G][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=0][active]
\_ 192:0:0:0 sdl 8:176 [active][ready]
\_ 191:0:0:0 sdf 8:80 [active][ready]
mpath152 (36000eb3945b8703a0000000000001431) dm-2 LEFTHAND,iSCSIDisk
[size=300G][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=0][active]
\_ 186:0:0:0 sdh 8:112 [active][ready]
\_ 185:0:0:0 sde 8:64 [active][ready]
mpath149 (36000eb3945b8703a0000000000001429) dm-5 LEFTHAND,iSCSIDisk
[size=300G][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=0][active]
\_ 189:0:0:0 sdc 8:32 [active][ready]
\_ 190:0:0:0 sdi 8:128 [active][ready]
mpath151 (36000eb3945b8703a000000000000142d) dm-6 LEFTHAND,iSCSIDisk
[size=300G][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=0][active]
\_ 188:0:0:0 sdj 8:144 [active][ready]
\_ 187:0:0:0 sdg 8:96 [active][ready]
mpath150 (36000eb3945b8703a0000000000001435) dm-4 LEFTHAND,iSCSIDisk
[size=200G][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=0][active]
\_ 184:0:0:0 sdk 8:160 [active][ready]
\_ 183:0:0:0 sdd 8:48 [active][ready]
[-- Attachment #1.2: Type: text/html, Size: 14680 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: Question regarding failback option in multipath.conf 2009-09-30 16:41 Question regarding failback option in multipath.conf Eli Klein @ 2009-09-30 18:51 ` Eli Klein 2009-09-30 19:07 ` John Brier 1 sibling, 0 replies; 11+ messages in thread From: Eli Klein @ 2009-09-30 18:51 UTC (permalink / raw) To: dm-devel [-- Attachment #1.1: Type: text/plain, Size: 3350 bytes --] Sorry, left off a few key details: I'm running the following: redhat 5.3 x86_64 device-mapper-1.02.28-2.el5 device-mapper-multipath-0.4.7-23.el5_3.4 Let me know if there are other details that would be helpful. -Eli On Sep 30, 2009, at 10:41 AM, Eli Klein wrote: > I'm running into an issue where the failback option in > multipath.conf is being ignored. I've tried to set this to a value > > 0 to cause dm to pause before reinstating a recovered path, but it > reinstates the path immediately. The same is true when setting the > value to "manual", the path is reinstated immediately. The delay is > most useful when a ethernet switch has failed or rebooted. During > the boot of the switch, the interface comes up and drops again > multiple times. I'd love to be able to introduce a delay before DM > marks the path as reinstated after a recovery. This would save me > the hassle of running into I/O errors (and occasional filesystem RO) > as the path bounces while the switch is booting. > > Thanks in advance for any help or suggestions! > > -Eli > > I've included my multipath.conf as well as output from multipath -ll > below: > > multipath.conf: > > blacklist { > devnode "sda$" > # devnode "*" > } > > ## By default, devices with vendor = "IBM" and product = "S/390.*" are > ## blacklisted. To enable mulitpathing on these devies, uncomment the > ## following lines. > #blacklist_exceptions { > # device { > # vendor "IBM" > # product "S/390.*" > # } > #} > > ## Use user friendly names, instead of using WWIDs as names. > defaults { > user_friendly_names yes > } > ## > ## Here is an example of how to configure some standard options. > ## > # > defaults { > udev_dir /dev > polling_interval 10 > selector "round-robin 0" > path_grouping_policy multibus > getuid_callout "/sbin/scsi_id -g -u -s /block/%n" > prio_callout /bin/true > path_checker readsector0 > rr_min_io 10 > rr_weight priorities > failback 120 > features "1 queue_if_no_path" > no_path_retry 1 > user_friendly_name yes > } > > multipath -ll: > > mpath2 (36000eb3945b8703a00000000000000f4) dm-3 LEFTHAND,iSCSIDisk > [size=400G][features=1 queue_if_no_path][hwhandler=0][rw] > \_ round-robin 0 [prio=0][active] > \_ 192:0:0:0 sdl 8:176 [active][ready] > \_ 191:0:0:0 sdf 8:80 [active][ready] > mpath152 (36000eb3945b8703a0000000000001431) dm-2 LEFTHAND,iSCSIDisk > [size=300G][features=1 queue_if_no_path][hwhandler=0][rw] > \_ round-robin 0 [prio=0][active] > \_ 186:0:0:0 sdh 8:112 [active][ready] > \_ 185:0:0:0 sde 8:64 [active][ready] > mpath149 (36000eb3945b8703a0000000000001429) dm-5 LEFTHAND,iSCSIDisk > [size=300G][features=1 queue_if_no_path][hwhandler=0][rw] > \_ round-robin 0 [prio=0][active] > \_ 189:0:0:0 sdc 8:32 [active][ready] > \_ 190:0:0:0 sdi 8:128 [active][ready] > mpath151 (36000eb3945b8703a000000000000142d) dm-6 LEFTHAND,iSCSIDisk > [size=300G][features=1 queue_if_no_path][hwhandler=0][rw] > \_ round-robin 0 [prio=0][active] > \_ 188:0:0:0 sdj 8:144 [active][ready] > \_ 187:0:0:0 sdg 8:96 [active][ready] > mpath150 (36000eb3945b8703a0000000000001435) dm-4 LEFTHAND,iSCSIDisk > [size=200G][features=1 queue_if_no_path][hwhandler=0][rw] > \_ round-robin 0 [prio=0][active] > \_ 184:0:0:0 sdk 8:160 [active][ready] > \_ 183:0:0:0 sdd 8:48 [active][ready] [-- Attachment #1.2: Type: text/html, Size: 15290 bytes --] [-- Attachment #2: Type: text/plain, Size: 0 bytes --] ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Question regarding failback option in multipath.conf 2009-09-30 16:41 Question regarding failback option in multipath.conf Eli Klein 2009-09-30 18:51 ` Eli Klein @ 2009-09-30 19:07 ` John Brier 2009-09-30 19:16 ` Eli Klein 1 sibling, 1 reply; 11+ messages in thread From: John Brier @ 2009-09-30 19:07 UTC (permalink / raw) To: device-mapper development On 09/30/2009 12:41 PM, Eli Klein wrote: > I'm running into an issue where the failback option in multipath.conf is > being ignored. I've tried to set this to a value > 0 to cause dm to > pause before reinstating a recovered path, but it reinstates the path > immediately. The same is true when setting the value to "manual", the > path is reinstated immediately. The delay is most useful when a ethernet > switch has failed or rebooted. During the boot of the switch, the > interface comes up and drops again multiple times. I'd love to be able > to introduce a delay before DM marks the path as reinstated after a > recovery. This would save me the hassle of running into I/O errors (and > occasional filesystem RO) as the path bounces while the switch is booting. > > Thanks in advance for any help or suggestions! > > -Eli > > I've included my multipath.conf as well as output from multipath -ll below: > > multipath.conf: > > blacklist { > devnode "sda$" > # devnode "*" > } > > ## By default, devices with vendor = "IBM" and product = "S/390.*" are > ## blacklisted. To enable mulitpathing on these devies, uncomment the > ## following lines. > #blacklist_exceptions { > # device { > # vendor "IBM" > # product "S/390.*" > # } > #} > > ## Use user friendly names, instead of using WWIDs as names. > defaults { > user_friendly_names yes > } > ## > ## Here is an example of how to configure some standard options. > ## > # > defaults { > udev_dir /dev > polling_interval 10 > selector "round-robin 0" > path_grouping_policy multibus > getuid_callout "/sbin/scsi_id -g -u -s /block/%n" > prio_callout /bin/true > path_checker readsector0 > rr_min_io 10 > rr_weight priorities > failback 120 > features "1 queue_if_no_path" > no_path_retry 1 > user_friendly_name yes > } It looks like you have two defaults {} sections. Is that allowed? Maybe multipath is only picking up the first one? I'd remove the first one/comment out and put user_friendly_names yes in the second one. Also I think multipath -v3 -d will show you what settings would be applied so you don't have to test the behavior by cycling your ethernet switch. For example on one of my systems multipath -v3 shows mpath1: pgfailback = -2 (controller setting) After you have it configured right run multipath -v3 without the -d (dry run) Can someone confirm if pgfailback from multipath -v3 output indicates the current setting of failback that multipath is using? John Brier ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Question regarding failback option in multipath.conf 2009-09-30 19:07 ` John Brier @ 2009-09-30 19:16 ` Eli Klein 2009-09-30 19:24 ` John Brier 0 siblings, 1 reply; 11+ messages in thread From: Eli Klein @ 2009-09-30 19:16 UTC (permalink / raw) To: device-mapper development [-- Attachment #1.1: Type: text/plain, Size: 3338 bytes --] On Sep 30, 2009, at 1:07 PM, John Brier wrote: > On 09/30/2009 12:41 PM, Eli Klein wrote: >> I'm running into an issue where the failback option in >> multipath.conf is >> being ignored. I've tried to set this to a value > 0 to cause dm to >> pause before reinstating a recovered path, but it reinstates the path >> immediately. The same is true when setting the value to "manual", the >> path is reinstated immediately. The delay is most useful when a >> ethernet >> switch has failed or rebooted. During the boot of the switch, the >> interface comes up and drops again multiple times. I'd love to be >> able >> to introduce a delay before DM marks the path as reinstated after a >> recovery. This would save me the hassle of running into I/O errors >> (and >> occasional filesystem RO) as the path bounces while the switch is >> booting. >> >> Thanks in advance for any help or suggestions! >> >> -Eli >> >> I've included my multipath.conf as well as output from multipath - >> ll below: >> >> multipath.conf: >> >> blacklist { >> devnode "sda$" >> # devnode "*" >> } >> >> ## By default, devices with vendor = "IBM" and product = "S/390.*" >> are >> ## blacklisted. To enable mulitpathing on these devies, uncomment the >> ## following lines. >> #blacklist_exceptions { >> # device { >> # vendor "IBM" >> # product "S/390.*" >> # } >> #} >> >> ## Use user friendly names, instead of using WWIDs as names. >> defaults { >> user_friendly_names yes >> } >> ## >> ## Here is an example of how to configure some standard options. >> ## >> # >> defaults { >> udev_dir /dev >> polling_interval 10 >> selector "round-robin 0" >> path_grouping_policy multibus >> getuid_callout "/sbin/scsi_id -g -u -s /block/%n" >> prio_callout /bin/true >> path_checker readsector0 >> rr_min_io 10 >> rr_weight priorities >> failback 120 >> features "1 queue_if_no_path" >> no_path_retry 1 >> user_friendly_name yes >> } > > It looks like you have two defaults {} sections. Is that allowed? > Maybe multipath is only picking up the first one? I'd remove the > first one/comment out and put user_friendly_names yes in the second > one. > > Also I think multipath -v3 -d will show you what settings would be > applied so you don't have to test the behavior by cycling your > ethernet switch. > > For example on one of my systems multipath -v3 shows > mpath1: pgfailback = -2 (controller setting) > > > After you have it configured right run multipath -v3 without the -d > (dry run) > > Can someone confirm if pgfailback from multipath -v3 output > indicates the current setting of failback that multipath is using? > > John Brier Here's the abbreviated output from multipath -v3: mpath1: pgfailback = 120 (config file default) mpath1: pgpolicy = multibus (config file default) mpath1: selector = round-robin 0 (internal default) mpath1: features = 1 queue_if_no_path (internal default) mpath1: hwhandler = 0 (internal default) mpath1: rr_weight = 2 (config file default) mpath1: minio = 10 (config file default) mpath1: no_path_retry = 1 (config file default) pg_timeout = NONE (internal default) mpath1: set ACT_NOTHING (map unchanged) It's definitely picking up the settings correctly from multipath.conf, but the paths are still reinstated immediately once they're reconnected (even if it's just for a split second). -Eli [-- Attachment #1.2: Type: text/html, Size: 5949 bytes --] [-- Attachment #2: Type: text/plain, Size: 0 bytes --] ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Question regarding failback option in multipath.conf 2009-09-30 19:16 ` Eli Klein @ 2009-09-30 19:24 ` John Brier 2009-09-30 19:36 ` Eli Klein 0 siblings, 1 reply; 11+ messages in thread From: John Brier @ 2009-09-30 19:24 UTC (permalink / raw) To: device-mapper development On 09/30/2009 03:16 PM, Eli Klein wrote: > > Here's the abbreviated output from multipath -v3: > > mpath1: pgfailback = 120 (config file default) > mpath1: pgpolicy = multibus (config file default) > mpath1: selector = round-robin 0 (internal default) > mpath1: features = 1 queue_if_no_path (internal default) > mpath1: hwhandler = 0 (internal default) > mpath1: rr_weight = 2 (config file default) > mpath1: minio = 10 (config file default) > mpath1: no_path_retry = 1 (config file default) > pg_timeout = NONE (internal default) > mpath1: set ACT_NOTHING (map unchanged) > > It's definitely picking up the settings correctly from multipath.conf, > but the paths are still reinstated immediately once they're reconnected > (even if it's just for a split second). > What does /var/log/messages look like when this happens? Since you changed failback to 120 did you restart multipathd or restart the box? John Brier ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Question regarding failback option in multipath.conf 2009-09-30 19:24 ` John Brier @ 2009-09-30 19:36 ` Eli Klein 2009-10-01 21:16 ` Eli Klein 0 siblings, 1 reply; 11+ messages in thread From: Eli Klein @ 2009-09-30 19:36 UTC (permalink / raw) To: device-mapper development [-- Attachment #1.1: Type: text/plain, Size: 6212 bytes --] On Sep 30, 2009, at 1:24 PM, John Brier wrote: > On 09/30/2009 03:16 PM, Eli Klein wrote: >> >> Here's the abbreviated output from multipath -v3: >> >> mpath1: pgfailback = 120 (config file default) >> mpath1: pgpolicy = multibus (config file default) >> mpath1: selector = round-robin 0 (internal default) >> mpath1: features = 1 queue_if_no_path (internal default) >> mpath1: hwhandler = 0 (internal default) >> mpath1: rr_weight = 2 (config file default) >> mpath1: minio = 10 (config file default) >> mpath1: no_path_retry = 1 (config file default) >> pg_timeout = NONE (internal default) >> mpath1: set ACT_NOTHING (map unchanged) >> >> It's definitely picking up the settings correctly from >> multipath.conf, >> but the paths are still reinstated immediately once they're >> reconnected >> (even if it's just for a split second). >> > > What does /var/log/messages look like when this happens? Since you > changed failback to 120 did you restart multipathd or restart the box? > > John Brier > > -- > dm-devel mailing list > dm-devel@redhat.com > https://www.redhat.com/mailman/listinfo/dm-devel I've tried rebooting, restarting multipath (and iscsid), flushing multipath (-F), removing all the iscsi targets completely and then reinitializing the targets. Nothing changes the behavior. Here's output from /var/log/messages.. note the time between when the link becomes active (13:31:08) to when the path is reinstated (13:31:15): Sep 30 13:30:28 testbox kernel: connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4470061909, last ping 4470066909, now 4470071909 Sep 30 13:30:28 testbox kernel: connection7:0: detected conn error (1011) Sep 30 13:30:28 testbox multipathd: sdf: readsector0 checker reports path is down Sep 30 13:30:28 testbox multipathd: checker failed path 8:80 in map mpath0 Sep 30 13:30:28 testbox multipathd: mpath0: remaining active paths: 1 Sep 30 13:30:28 testbox kernel: device-mapper: multipath: Failing path 8:80. Sep 30 13:30:28 testbox iscsid: Kernel reported iSCSI connection 7:0 error (1011) state (3) Sep 30 13:30:29 testbox kernel: connection9:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4470063232, last ping 4470068232, now 4470073232 Sep 30 13:30:29 testbox kernel: connection9:0: detected conn error (1011) Sep 30 13:30:29 testbox multipathd: sdg: readsector0 checker reports path is down Sep 30 13:30:29 testbox multipathd: checker failed path 8:96 in map mpath1 Sep 30 13:30:29 testbox multipathd: mpath1: remaining active paths: 1 Sep 30 13:30:29 testbox kernel: device-mapper: multipath: Failing path 8:96. Sep 30 13:30:30 testbox kernel: connection11:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4470064373, last ping 4470069373, now 4470074373 Sep 30 13:30:30 testbox kernel: connection11:0: detected conn error (1011) Sep 30 13:30:30 testbox iscsid: Kernel reported iSCSI connection 9:0 error (1011) state (3) Sep 30 13:30:30 testbox multipathd: sdh: readsector0 checker reports path is down Sep 30 13:30:30 testbox multipathd: checker failed path 8:112 in map mpath2 Sep 30 13:30:30 testbox kernel: device-mapper: multipath: Failing path 8:112. Sep 30 13:30:30 testbox multipathd: mpath2: remaining active paths: 1 Sep 30 13:30:30 testbox multipathd: dm-4: add map (uevent) Sep 30 13:30:30 testbox multipathd: dm-4: devmap already registered Sep 30 13:30:30 testbox multipathd: dm-2: add map (uevent) Sep 30 13:30:30 testbox multipathd: dm-2: devmap already registered Sep 30 13:30:30 testbox multipathd: dm-3: add map (uevent) Sep 30 13:30:30 testbox multipathd: dm-3: devmap already registered Sep 30 13:30:31 testbox iscsid: Kernel reported iSCSI connection 11:0 error (1011) state (3) Sep 30 13:30:43 testbox kernel: session7: session recovery timed out after 15 secs Sep 30 13:30:43 testbox multipathd: sdf: readsector0 checker reports path is down Sep 30 13:30:44 testbox kernel: session9: session recovery timed out after 15 secs Sep 30 13:30:44 testbox multipathd: sdg: readsector0 checker reports path is down Sep 30 13:30:45 testbox kernel: session11: session recovery timed out after 15 secs Sep 30 13:30:45 testbox kernel: sd 13:0:0:0: SCSI error: return code = 0x000f0000 Sep 30 13:30:45 testbox kernel: end_request: I/O error, dev sdh, sector 407978223 Sep 30 13:30:45 testbox multipathd: sdh: readsector0 checker reports path is down Sep 30 13:30:55 testbox multipathd: sdf: readsector0 checker reports path is down Sep 30 13:31:05 testbox multipathd: sdg: readsector0 checker reports path is down Sep 30 13:31:05 testbox multipathd: sdh: readsector0 checker reports path is down Sep 30 13:31:05 testbox multipathd: sdf: readsector0 checker reports path is down Sep 30 13:31:05 testbox multipathd: sdg: readsector0 checker reports path is down Sep 30 13:31:05 testbox multipathd: sdh: readsector0 checker reports path is down Sep 30 13:31:08 testbox iscsid: connection9:0 is operational after recovery (3 attempts) Sep 30 13:31:08 testbox iscsid: connection11:0 is operational after recovery (3 attempts) Sep 30 13:31:11 testbox iscsid: connection7:0 is operational after recovery (3 attempts) Sep 30 13:31:15 testbox multipathd: sdf: readsector0 checker reports path is up Sep 30 13:31:15 testbox multipathd: 8:80: reinstated Sep 30 13:31:15 testbox multipathd: mpath0: remaining active paths: 2 Sep 30 13:31:15 testbox multipathd: sdg: readsector0 checker reports path is up Sep 30 13:31:15 testbox multipathd: 8:96: reinstated Sep 30 13:31:15 testbox multipathd: mpath1: remaining active paths: 2 Sep 30 13:31:15 testbox multipathd: sdh: readsector0 checker reports path is up Sep 30 13:31:15 testbox multipathd: 8:112: reinstated Sep 30 13:31:15 testbox multipathd: mpath2: remaining active paths: 2 Sep 30 13:31:15 testbox multipathd: dm-4: add map (uevent) Sep 30 13:31:15 testbox multipathd: dm-4: devmap already registered Sep 30 13:31:15 testbox multipathd: dm-2: add map (uevent) Sep 30 13:31:15 testbox multipathd: dm-2: devmap already registered Sep 30 13:31:15 testbox multipathd: dm-3: add map (uevent) Sep 30 13:31:15 testbox multipathd: dm-3: devmap already registered [-- Attachment #1.2: Type: text/html, Size: 15787 bytes --] [-- Attachment #2: Type: text/plain, Size: 0 bytes --] ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Question regarding failback option in multipath.conf 2009-09-30 19:36 ` Eli Klein @ 2009-10-01 21:16 ` Eli Klein 2009-10-02 0:39 ` John A. Sullivan III 0 siblings, 1 reply; 11+ messages in thread From: Eli Klein @ 2009-10-01 21:16 UTC (permalink / raw) To: device-mapper development [-- Attachment #1.1: Type: text/plain, Size: 6483 bytes --] Any ideas on this? Not sure if this e-mail made it out to the list. Thanks! -Eli On Wed, Sep 30, 2009 at 1:36 PM, Eli Klein <elijah@aclue.com> wrote: > On Sep 30, 2009, at 1:24 PM, John Brier wrote: > > On 09/30/2009 03:16 PM, Eli Klein wrote: > > > Here's the abbreviated output from multipath -v3: > > > mpath1: pgfailback = 120 (config file default) > > mpath1: pgpolicy = multibus (config file default) > > mpath1: selector = round-robin 0 (internal default) > > mpath1: features = 1 queue_if_no_path (internal default) > > mpath1: hwhandler = 0 (internal default) > > mpath1: rr_weight = 2 (config file default) > > mpath1: minio = 10 (config file default) > > mpath1: no_path_retry = 1 (config file default) > > pg_timeout = NONE (internal default) > > mpath1: set ACT_NOTHING (map unchanged) > > > It's definitely picking up the settings correctly from multipath.conf, > > but the paths are still reinstated immediately once they're reconnected > > (even if it's just for a split second). > > > > What does /var/log/messages look like when this happens? Since you changed > failback to 120 did you restart multipathd or restart the box? > > John Brier > > -- > dm-devel mailing list > dm-devel@redhat.com > https://www.redhat.com/mailman/listinfo/dm-devel > > > I've tried rebooting, restarting multipath (and iscsid), flushing multipath > (-F), removing all the iscsi targets completely and then reinitializing the > targets. Nothing changes the behavior. Here's output from > /var/log/messages.. note the time between when the link becomes active > (13:31:08) to when the path is reinstated (13:31:15): > > Sep 30 13:30:28 testbox kernel: connection7:0: ping timeout of 5 secs > expired, recv timeout 5, last rx 4470061909, last ping 4470066909, now > 4470071909 > Sep 30 13:30:28 testbox kernel: connection7:0: detected conn error (1011) > Sep 30 13:30:28 testbox multipathd: sdf: readsector0 checker reports path > is down > Sep 30 13:30:28 testbox multipathd: checker failed path 8:80 in map mpath0 > Sep 30 13:30:28 testbox multipathd: mpath0: remaining active paths: 1 > Sep 30 13:30:28 testbox kernel: device-mapper: multipath: Failing path > 8:80. > Sep 30 13:30:28 testbox iscsid: Kernel reported iSCSI connection 7:0 error > (1011) state (3) > Sep 30 13:30:29 testbox kernel: connection9:0: ping timeout of 5 secs > expired, recv timeout 5, last rx 4470063232, last ping 4470068232, now > 4470073232 > Sep 30 13:30:29 testbox kernel: connection9:0: detected conn error (1011) > Sep 30 13:30:29 testbox multipathd: sdg: readsector0 checker reports path > is down > Sep 30 13:30:29 testbox multipathd: checker failed path 8:96 in map mpath1 > Sep 30 13:30:29 testbox multipathd: mpath1: remaining active paths: 1 > Sep 30 13:30:29 testbox kernel: device-mapper: multipath: Failing path > 8:96. > Sep 30 13:30:30 testbox kernel: connection11:0: ping timeout of 5 secs > expired, recv timeout 5, last rx 4470064373, last ping 4470069373, now > 4470074373 > Sep 30 13:30:30 testbox kernel: connection11:0: detected conn error (1011) > Sep 30 13:30:30 testbox iscsid: Kernel reported iSCSI connection 9:0 error > (1011) state (3) > Sep 30 13:30:30 testbox multipathd: sdh: readsector0 checker reports path > is down > Sep 30 13:30:30 testbox multipathd: checker failed path 8:112 in map mpath2 > Sep 30 13:30:30 testbox kernel: device-mapper: multipath: Failing path > 8:112. > Sep 30 13:30:30 testbox multipathd: mpath2: remaining active paths: 1 > Sep 30 13:30:30 testbox multipathd: dm-4: add map (uevent) > Sep 30 13:30:30 testbox multipathd: dm-4: devmap already registered > Sep 30 13:30:30 testbox multipathd: dm-2: add map (uevent) > Sep 30 13:30:30 testbox multipathd: dm-2: devmap already registered > Sep 30 13:30:30 testbox multipathd: dm-3: add map (uevent) > Sep 30 13:30:30 testbox multipathd: dm-3: devmap already registered > Sep 30 13:30:31 testbox iscsid: Kernel reported iSCSI connection 11:0 error > (1011) state (3) > Sep 30 13:30:43 testbox kernel: session7: session recovery timed out after > 15 secs > Sep 30 13:30:43 testbox multipathd: sdf: readsector0 checker reports path > is down > Sep 30 13:30:44 testbox kernel: session9: session recovery timed out after > 15 secs > Sep 30 13:30:44 testbox multipathd: sdg: readsector0 checker reports path > is down > Sep 30 13:30:45 testbox kernel: session11: session recovery timed out > after 15 secs > Sep 30 13:30:45 testbox kernel: sd 13:0:0:0: SCSI error: return code = > 0x000f0000 > Sep 30 13:30:45 testbox kernel: end_request: I/O error, dev sdh, sector > 407978223 > Sep 30 13:30:45 testbox multipathd: sdh: readsector0 checker reports path > is down > Sep 30 13:30:55 testbox multipathd: sdf: readsector0 checker reports path > is down > Sep 30 13:31:05 testbox multipathd: sdg: readsector0 checker reports path > is down > Sep 30 13:31:05 testbox multipathd: sdh: readsector0 checker reports path > is down > Sep 30 13:31:05 testbox multipathd: sdf: readsector0 checker reports path > is down > Sep 30 13:31:05 testbox multipathd: sdg: readsector0 checker reports path > is down > Sep 30 13:31:05 testbox multipathd: sdh: readsector0 checker reports path > is down > Sep 30 13:31:08 testbox iscsid: connection9:0 is operational after recovery > (3 attempts) > Sep 30 13:31:08 testbox iscsid: connection11:0 is operational after > recovery (3 attempts) > Sep 30 13:31:11 testbox iscsid: connection7:0 is operational after recovery > (3 attempts) > Sep 30 13:31:15 testbox multipathd: sdf: readsector0 checker reports path > is up > Sep 30 13:31:15 testbox multipathd: 8:80: reinstated > Sep 30 13:31:15 testbox multipathd: mpath0: remaining active paths: 2 > Sep 30 13:31:15 testbox multipathd: sdg: readsector0 checker reports path > is up > Sep 30 13:31:15 testbox multipathd: 8:96: reinstated > Sep 30 13:31:15 testbox multipathd: mpath1: remaining active paths: 2 > Sep 30 13:31:15 testbox multipathd: sdh: readsector0 checker reports path > is up > Sep 30 13:31:15 testbox multipathd: 8:112: reinstated > Sep 30 13:31:15 testbox multipathd: mpath2: remaining active paths: 2 > Sep 30 13:31:15 testbox multipathd: dm-4: add map (uevent) > Sep 30 13:31:15 testbox multipathd: dm-4: devmap already registered > Sep 30 13:31:15 testbox multipathd: dm-2: add map (uevent) > Sep 30 13:31:15 testbox multipathd: dm-2: devmap already registered > Sep 30 13:31:15 testbox multipathd: dm-3: add map (uevent) > Sep 30 13:31:15 testbox multipathd: dm-3: devmap already registered > > [-- Attachment #1.2: Type: text/html, Size: 13668 bytes --] [-- Attachment #2: Type: text/plain, Size: 0 bytes --] ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Question regarding failback option in multipath.conf 2009-10-01 21:16 ` Eli Klein @ 2009-10-02 0:39 ` John A. Sullivan III 2009-10-02 1:01 ` Eli Klein 0 siblings, 1 reply; 11+ messages in thread From: John A. Sullivan III @ 2009-10-02 0:39 UTC (permalink / raw) To: device-mapper development I don't have the expertise to help very much but did you address the previous comment about duplicate default blocks? Good luck - John On Thu, 2009-10-01 at 15:16 -0600, Eli Klein wrote: > Any ideas on this? Not sure if this e-mail made it out to the list. > > > Thanks! > > > -Eli > > On Wed, Sep 30, 2009 at 1:36 PM, Eli Klein <elijah@aclue.com> wrote: > > On Sep 30, 2009, at 1:24 PM, John Brier wrote: > > > On 09/30/2009 03:16 PM, Eli Klein wrote: > > > > > > Here's the abbreviated output from multipath -v3: > > > > > > mpath1: pgfailback = 120 (config file default) > > > mpath1: pgpolicy = multibus (config file default) > > > mpath1: selector = round-robin 0 (internal default) > > > mpath1: features = 1 queue_if_no_path (internal default) > > > mpath1: hwhandler = 0 (internal default) > > > mpath1: rr_weight = 2 (config file default) > > > mpath1: minio = 10 (config file default) > > > mpath1: no_path_retry = 1 (config file default) > > > pg_timeout = NONE (internal default) > > > mpath1: set ACT_NOTHING (map unchanged) > > > > > > It's definitely picking up the settings correctly from > > > multipath.conf, > > > but the paths are still reinstated immediately once > > > they're reconnected > > > (even if it's just for a split second). > > > > > > > What does /var/log/messages look like when this happens? > > Since you changed failback to 120 did you restart multipathd > > or restart the box? > > > > John Brier > > > > -- > > dm-devel mailing list > > dm-devel@redhat.com > > https://www.redhat.com/mailman/listinfo/dm-devel > > > > > I've tried rebooting, restarting multipath (and iscsid), > flushing multipath (-F), removing all the iscsi targets > completely and then reinitializing the targets. Nothing > changes the behavior. Here's output from /var/log/messages.. > note the time between when the link becomes active (13:31:08) > to when the path is reinstated (13:31:15): > > > Sep 30 13:30:28 testbox kernel: connection7:0: ping timeout > of 5 secs expired, recv timeout 5, last rx 4470061909, last > ping 4470066909, now 4470071909 > Sep 30 13:30:28 testbox kernel: connection7:0: detected conn > error (1011) > Sep 30 13:30:28 testbox multipathd: sdf: readsector0 checker > reports path is down > Sep 30 13:30:28 testbox multipathd: checker failed path 8:80 > in map mpath0 > Sep 30 13:30:28 testbox multipathd: mpath0: remaining active > paths: 1 > Sep 30 13:30:28 testbox kernel: device-mapper: multipath: > Failing path 8:80. > Sep 30 13:30:28 testbox iscsid: Kernel reported iSCSI > connection 7:0 error (1011) state (3) > Sep 30 13:30:29 testbox kernel: connection9:0: ping timeout > of 5 secs expired, recv timeout 5, last rx 4470063232, last > ping 4470068232, now 4470073232 > Sep 30 13:30:29 testbox kernel: connection9:0: detected conn > error (1011) > Sep 30 13:30:29 testbox multipathd: sdg: readsector0 checker > reports path is down > Sep 30 13:30:29 testbox multipathd: checker failed path 8:96 > in map mpath1 > Sep 30 13:30:29 testbox multipathd: mpath1: remaining active > paths: 1 > Sep 30 13:30:29 testbox kernel: device-mapper: multipath: > Failing path 8:96. > Sep 30 13:30:30 testbox kernel: connection11:0: ping timeout > of 5 secs expired, recv timeout 5, last rx 4470064373, last > ping 4470069373, now 4470074373 > Sep 30 13:30:30 testbox kernel: connection11:0: detected conn > error (1011) > Sep 30 13:30:30 testbox iscsid: Kernel reported iSCSI > connection 9:0 error (1011) state (3) > Sep 30 13:30:30 testbox multipathd: sdh: readsector0 checker > reports path is down > Sep 30 13:30:30 testbox multipathd: checker failed path 8:112 > in map mpath2 > Sep 30 13:30:30 testbox kernel: device-mapper: multipath: > Failing path 8:112. > Sep 30 13:30:30 testbox multipathd: mpath2: remaining active > paths: 1 > Sep 30 13:30:30 testbox multipathd: dm-4: add map (uevent) > Sep 30 13:30:30 testbox multipathd: dm-4: devmap already > registered > Sep 30 13:30:30 testbox multipathd: dm-2: add map (uevent) > Sep 30 13:30:30 testbox multipathd: dm-2: devmap already > registered > Sep 30 13:30:30 testbox multipathd: dm-3: add map (uevent) > Sep 30 13:30:30 testbox multipathd: dm-3: devmap already > registered > Sep 30 13:30:31 testbox iscsid: Kernel reported iSCSI > connection 11:0 error (1011) state (3) > Sep 30 13:30:43 testbox kernel: session7: session recovery > timed out after 15 secs > Sep 30 13:30:43 testbox multipathd: sdf: readsector0 checker > reports path is down > Sep 30 13:30:44 testbox kernel: session9: session recovery > timed out after 15 secs > Sep 30 13:30:44 testbox multipathd: sdg: readsector0 checker > reports path is down > Sep 30 13:30:45 testbox kernel: session11: session recovery > timed out after 15 secs > Sep 30 13:30:45 testbox kernel: sd 13:0:0:0: SCSI error: > return code = 0x000f0000 > Sep 30 13:30:45 testbox kernel: end_request: I/O error, dev > sdh, sector 407978223 > Sep 30 13:30:45 testbox multipathd: sdh: readsector0 checker > reports path is down > Sep 30 13:30:55 testbox multipathd: sdf: readsector0 checker > reports path is down > Sep 30 13:31:05 testbox multipathd: sdg: readsector0 checker > reports path is down > Sep 30 13:31:05 testbox multipathd: sdh: readsector0 checker > reports path is down > Sep 30 13:31:05 testbox multipathd: sdf: readsector0 checker > reports path is down > Sep 30 13:31:05 testbox multipathd: sdg: readsector0 checker > reports path is down > Sep 30 13:31:05 testbox multipathd: sdh: readsector0 checker > reports path is down > Sep 30 13:31:08 testbox iscsid: connection9:0 is operational > after recovery (3 attempts) > Sep 30 13:31:08 testbox iscsid: connection11:0 is operational > after recovery (3 attempts) > Sep 30 13:31:11 testbox iscsid: connection7:0 is operational > after recovery (3 attempts) > Sep 30 13:31:15 testbox multipathd: sdf: readsector0 checker > reports path is up > Sep 30 13:31:15 testbox multipathd: 8:80: reinstated > Sep 30 13:31:15 testbox multipathd: mpath0: remaining active > paths: 2 > Sep 30 13:31:15 testbox multipathd: sdg: readsector0 checker > reports path is up > Sep 30 13:31:15 testbox multipathd: 8:96: reinstated > Sep 30 13:31:15 testbox multipathd: mpath1: remaining active > paths: 2 > Sep 30 13:31:15 testbox multipathd: sdh: readsector0 checker > reports path is up > Sep 30 13:31:15 testbox multipathd: 8:112: reinstated > Sep 30 13:31:15 testbox multipathd: mpath2: remaining active > paths: 2 > Sep 30 13:31:15 testbox multipathd: dm-4: add map (uevent) > Sep 30 13:31:15 testbox multipathd: dm-4: devmap already > registered > Sep 30 13:31:15 testbox multipathd: dm-2: add map (uevent) > Sep 30 13:31:15 testbox multipathd: dm-2: devmap already > registered > Sep 30 13:31:15 testbox multipathd: dm-3: add map (uevent) > Sep 30 13:31:15 testbox multipathd: dm-3: devmap already > registered > > > > > -- > dm-devel mailing list > dm-devel@redhat.com > https://www.redhat.com/mailman/listinfo/dm-devel -- John A. Sullivan III Open Source Development Corporation +1 207-985-7880 jsullivan@opensourcedevel.com http://www.spiritualoutreach.com Making Christianity intelligible to secular society ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Question regarding failback option in multipath.conf 2009-10-02 0:39 ` John A. Sullivan III @ 2009-10-02 1:01 ` Eli Klein 2009-10-02 14:30 ` John Brier 0 siblings, 1 reply; 11+ messages in thread From: Eli Klein @ 2009-10-02 1:01 UTC (permalink / raw) To: device-mapper development [-- Attachment #1.1: Type: text/plain, Size: 9107 bytes --] Sorry, I forgot to mention that I did.. it didn't help. In addition, from the output of multipath -v3, multipathd is picking up all of the correct settings, even with the two separate default sections. -Eli On Thu, Oct 1, 2009 at 6:39 PM, John A. Sullivan III < jsullivan@opensourcedevel.com> wrote: > I don't have the expertise to help very much but did you address the > previous comment about duplicate default blocks? Good luck - John > > On Thu, 2009-10-01 at 15:16 -0600, Eli Klein wrote: > > Any ideas on this? Not sure if this e-mail made it out to the list. > > > > > > Thanks! > > > > > > -Eli > > > > On Wed, Sep 30, 2009 at 1:36 PM, Eli Klein <elijah@aclue.com> wrote: > > > > On Sep 30, 2009, at 1:24 PM, John Brier wrote: > > > > > On 09/30/2009 03:16 PM, Eli Klein wrote: > > > > > > > > Here's the abbreviated output from multipath -v3: > > > > > > > > mpath1: pgfailback = 120 (config file default) > > > > mpath1: pgpolicy = multibus (config file default) > > > > mpath1: selector = round-robin 0 (internal default) > > > > mpath1: features = 1 queue_if_no_path (internal default) > > > > mpath1: hwhandler = 0 (internal default) > > > > mpath1: rr_weight = 2 (config file default) > > > > mpath1: minio = 10 (config file default) > > > > mpath1: no_path_retry = 1 (config file default) > > > > pg_timeout = NONE (internal default) > > > > mpath1: set ACT_NOTHING (map unchanged) > > > > > > > > It's definitely picking up the settings correctly from > > > > multipath.conf, > > > > but the paths are still reinstated immediately once > > > > they're reconnected > > > > (even if it's just for a split second). > > > > > > > > > > What does /var/log/messages look like when this happens? > > > Since you changed failback to 120 did you restart multipathd > > > or restart the box? > > > > > > John Brier > > > > > > -- > > > dm-devel mailing list > > > dm-devel@redhat.com > > > https://www.redhat.com/mailman/listinfo/dm-devel > > > > > > > > > I've tried rebooting, restarting multipath (and iscsid), > > flushing multipath (-F), removing all the iscsi targets > > completely and then reinitializing the targets. Nothing > > changes the behavior. Here's output from /var/log/messages.. > > note the time between when the link becomes active (13:31:08) > > to when the path is reinstated (13:31:15): > > > > > > Sep 30 13:30:28 testbox kernel: connection7:0: ping timeout > > of 5 secs expired, recv timeout 5, last rx 4470061909, last > > ping 4470066909, now 4470071909 > > Sep 30 13:30:28 testbox kernel: connection7:0: detected conn > > error (1011) > > Sep 30 13:30:28 testbox multipathd: sdf: readsector0 checker > > reports path is down > > Sep 30 13:30:28 testbox multipathd: checker failed path 8:80 > > in map mpath0 > > Sep 30 13:30:28 testbox multipathd: mpath0: remaining active > > paths: 1 > > Sep 30 13:30:28 testbox kernel: device-mapper: multipath: > > Failing path 8:80. > > Sep 30 13:30:28 testbox iscsid: Kernel reported iSCSI > > connection 7:0 error (1011) state (3) > > Sep 30 13:30:29 testbox kernel: connection9:0: ping timeout > > of 5 secs expired, recv timeout 5, last rx 4470063232, last > > ping 4470068232, now 4470073232 > > Sep 30 13:30:29 testbox kernel: connection9:0: detected conn > > error (1011) > > Sep 30 13:30:29 testbox multipathd: sdg: readsector0 checker > > reports path is down > > Sep 30 13:30:29 testbox multipathd: checker failed path 8:96 > > in map mpath1 > > Sep 30 13:30:29 testbox multipathd: mpath1: remaining active > > paths: 1 > > Sep 30 13:30:29 testbox kernel: device-mapper: multipath: > > Failing path 8:96. > > Sep 30 13:30:30 testbox kernel: connection11:0: ping timeout > > of 5 secs expired, recv timeout 5, last rx 4470064373, last > > ping 4470069373, now 4470074373 > > Sep 30 13:30:30 testbox kernel: connection11:0: detected conn > > error (1011) > > Sep 30 13:30:30 testbox iscsid: Kernel reported iSCSI > > connection 9:0 error (1011) state (3) > > Sep 30 13:30:30 testbox multipathd: sdh: readsector0 checker > > reports path is down > > Sep 30 13:30:30 testbox multipathd: checker failed path 8:112 > > in map mpath2 > > Sep 30 13:30:30 testbox kernel: device-mapper: multipath: > > Failing path 8:112. > > Sep 30 13:30:30 testbox multipathd: mpath2: remaining active > > paths: 1 > > Sep 30 13:30:30 testbox multipathd: dm-4: add map (uevent) > > Sep 30 13:30:30 testbox multipathd: dm-4: devmap already > > registered > > Sep 30 13:30:30 testbox multipathd: dm-2: add map (uevent) > > Sep 30 13:30:30 testbox multipathd: dm-2: devmap already > > registered > > Sep 30 13:30:30 testbox multipathd: dm-3: add map (uevent) > > Sep 30 13:30:30 testbox multipathd: dm-3: devmap already > > registered > > Sep 30 13:30:31 testbox iscsid: Kernel reported iSCSI > > connection 11:0 error (1011) state (3) > > Sep 30 13:30:43 testbox kernel: session7: session recovery > > timed out after 15 secs > > Sep 30 13:30:43 testbox multipathd: sdf: readsector0 checker > > reports path is down > > Sep 30 13:30:44 testbox kernel: session9: session recovery > > timed out after 15 secs > > Sep 30 13:30:44 testbox multipathd: sdg: readsector0 checker > > reports path is down > > Sep 30 13:30:45 testbox kernel: session11: session recovery > > timed out after 15 secs > > Sep 30 13:30:45 testbox kernel: sd 13:0:0:0: SCSI error: > > return code = 0x000f0000 > > Sep 30 13:30:45 testbox kernel: end_request: I/O error, dev > > sdh, sector 407978223 > > Sep 30 13:30:45 testbox multipathd: sdh: readsector0 checker > > reports path is down > > Sep 30 13:30:55 testbox multipathd: sdf: readsector0 checker > > reports path is down > > Sep 30 13:31:05 testbox multipathd: sdg: readsector0 checker > > reports path is down > > Sep 30 13:31:05 testbox multipathd: sdh: readsector0 checker > > reports path is down > > Sep 30 13:31:05 testbox multipathd: sdf: readsector0 checker > > reports path is down > > Sep 30 13:31:05 testbox multipathd: sdg: readsector0 checker > > reports path is down > > Sep 30 13:31:05 testbox multipathd: sdh: readsector0 checker > > reports path is down > > Sep 30 13:31:08 testbox iscsid: connection9:0 is operational > > after recovery (3 attempts) > > Sep 30 13:31:08 testbox iscsid: connection11:0 is operational > > after recovery (3 attempts) > > Sep 30 13:31:11 testbox iscsid: connection7:0 is operational > > after recovery (3 attempts) > > Sep 30 13:31:15 testbox multipathd: sdf: readsector0 checker > > reports path is up > > Sep 30 13:31:15 testbox multipathd: 8:80: reinstated > > Sep 30 13:31:15 testbox multipathd: mpath0: remaining active > > paths: 2 > > Sep 30 13:31:15 testbox multipathd: sdg: readsector0 checker > > reports path is up > > Sep 30 13:31:15 testbox multipathd: 8:96: reinstated > > Sep 30 13:31:15 testbox multipathd: mpath1: remaining active > > paths: 2 > > Sep 30 13:31:15 testbox multipathd: sdh: readsector0 checker > > reports path is up > > Sep 30 13:31:15 testbox multipathd: 8:112: reinstated > > Sep 30 13:31:15 testbox multipathd: mpath2: remaining active > > paths: 2 > > Sep 30 13:31:15 testbox multipathd: dm-4: add map (uevent) > > Sep 30 13:31:15 testbox multipathd: dm-4: devmap already > > registered > > Sep 30 13:31:15 testbox multipathd: dm-2: add map (uevent) > > Sep 30 13:31:15 testbox multipathd: dm-2: devmap already > > registered > > Sep 30 13:31:15 testbox multipathd: dm-3: add map (uevent) > > Sep 30 13:31:15 testbox multipathd: dm-3: devmap already > > registered > > > > > > > > > > -- > > dm-devel mailing list > > dm-devel@redhat.com > > https://www.redhat.com/mailman/listinfo/dm-devel > -- > John A. Sullivan III > Open Source Development Corporation > +1 207-985-7880 > jsullivan@opensourcedevel.com > > http://www.spiritualoutreach.com > Making Christianity intelligible to secular society > > -- > dm-devel mailing list > dm-devel@redhat.com > https://www.redhat.com/mailman/listinfo/dm-devel > [-- Attachment #1.2: Type: text/html, Size: 11339 bytes --] [-- Attachment #2: Type: text/plain, Size: 0 bytes --] ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Question regarding failback option in multipath.conf 2009-10-02 1:01 ` Eli Klein @ 2009-10-02 14:30 ` John Brier 2009-10-02 14:40 ` Eli Klein 0 siblings, 1 reply; 11+ messages in thread From: John Brier @ 2009-10-02 14:30 UTC (permalink / raw) To: device-mapper development On 10/01/2009 09:01 PM, Eli Klein wrote: > Sorry, I forgot to mention that I did.. it didn't help. > In addition, from the output of multipath -v3, multipathd is picking up all > of the correct settings, even with the two separate default sections. > It seems like you set it all up right but failback isn't working like it *seems* it should. (I have never needed it) If you're interested in a hack.. Since you don't seem to care how long it takes to failover, you could do the *opposite* of what this kbase recommends: How can I improve the failover time of a faulty path when using device-mapper-multipath over iSCSI? http://kbase.redhat.com/faq/docs/DOC-2877 Aside from that I would suggest you open a support case with Red Hat if the box is covered under a support contract. John Brier ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Question regarding failback option in multipath.conf 2009-10-02 14:30 ` John Brier @ 2009-10-02 14:40 ` Eli Klein 0 siblings, 0 replies; 11+ messages in thread From: Eli Klein @ 2009-10-02 14:40 UTC (permalink / raw) To: device-mapper development [-- Attachment #1.1: Type: text/plain, Size: 1645 bytes --] On Fri, Oct 2, 2009 at 8:30 AM, John Brier <jbrier@redhat.com> wrote: > On 10/01/2009 09:01 PM, Eli Klein wrote: > >> Sorry, I forgot to mention that I did.. it didn't help. >> In addition, from the output of multipath -v3, multipathd is picking up >> all >> of the correct settings, even with the two separate default sections. >> >> > It seems like you set it all up right but failback isn't working like it > *seems* it should. (I have never needed it) If you're interested in a hack.. > > Since you don't seem to care how long it takes to failover, you could do > the *opposite* of what this kbase recommends: > > How can I improve the failover time of a faulty path when using > device-mapper-multipath over iSCSI? > > http://kbase.redhat.com/faq/docs/DOC-2877 > > > Aside from that I would suggest you open a support case with Red Hat if the > box is covered under a support contract. > > > John Brier > > -- > dm-devel mailing list > dm-devel@redhat.com > https://www.redhat.com/mailman/listinfo/dm-devel > I've seen that doc before (it was helpful!). Unfortunately, I *do* care about how long it takes for the initial failover. I have this configured to take 15 seconds at the moment. One thing that's interesting is that even when I had "node.session.timeo.replacement_timeout" set to 120 seconds, the failback was still immediate. The initial failover would take at minimum 120 seconds. All of my problems seem to be cause by what appears to be a failback parameter that doesn't actually have any effect. I'll have to open up a support case to get to the bottom of the failback issues. Thank you very much for your help! -Eli [-- Attachment #1.2: Type: text/html, Size: 3054 bytes --] [-- Attachment #2: Type: text/plain, Size: 0 bytes --] ^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2009-10-02 14:40 UTC | newest] Thread overview: 11+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2009-09-30 16:41 Question regarding failback option in multipath.conf Eli Klein 2009-09-30 18:51 ` Eli Klein 2009-09-30 19:07 ` John Brier 2009-09-30 19:16 ` Eli Klein 2009-09-30 19:24 ` John Brier 2009-09-30 19:36 ` Eli Klein 2009-10-01 21:16 ` Eli Klein 2009-10-02 0:39 ` John A. Sullivan III 2009-10-02 1:01 ` Eli Klein 2009-10-02 14:30 ` John Brier 2009-10-02 14:40 ` Eli Klein
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.