| Message ID | 20130503175948.GO6253@ether.msp.redhat.com (mailing list archive) |
|---|---|
| State | Deferred, archived |
| Headers | show |
On 05/03/2013 07:59 PM, Benjamin Marzinski wrote: > Due to some code being placed inside the wrong block, the number of > seconds to wait between path checks (pp->tick), was only getting set to > the path's individual check interval if that wasn't equal to the max > check interval. Otherwise it was using the default for a failed path. > This patch makes sure that pp->ticks always always gets set correctly > for active paths. > > Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com> Acked-by: Hannes Reinecke <hare@suse.de> Cheers, Hannes
diff --git a/multipathd/main.c b/multipathd/main.c index 440d254..9d52465 100644 --- a/multipathd/main.c +++ b/multipathd/main.c @@ -1220,10 +1220,10 @@ check_path (struct vectors * vecs, struct path * pp) else pp->checkint = conf->max_checkint; - pp->tick = pp->checkint; condlog(4, "%s: delay next check %is", - pp->dev_t, pp->tick); + pp->dev_t, pp->checkint); } + pp->tick = pp->checkint; } } else if (newstate == PATH_DOWN) {
Due to some code being placed inside the wrong block, the number of seconds to wait between path checks (pp->tick), was only getting set to the path's individual check interval if that wasn't equal to the max check interval. Otherwise it was using the default for a failed path. This patch makes sure that pp->ticks always always gets set correctly for active paths. Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com> --- multipathd/main.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)