All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Marzinski <bmarzins@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH multipath-tools-0.4.7.rhel5.13 1/1] multipathd excessive path checker logging
Date: Fri, 26 Jun 2009 15:50:57 -0500	[thread overview]
Message-ID: <20090626205057.GL3172@ether.msp.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0906251344350.4229@e-smith.charlieb.ott.istop.com>

On Thu, Jun 25, 2009 at 01:50:51PM -0400, Charlie Brady wrote:
>
> multipathd logs a path checker message whenever state changes. But it also 
> logs every non-changed message when verbosity is >=4 and newstate is 
> PATH_UP or PATH_GHOST, and every non-changed message when verbosity is >= 2 
> and newstate is PATH_DOWN.
>
> I believe that the message should only be logged, once, when state changes.

I disagree.  If you look at the stuff that gets logged when verbosity >=
4, you'll see that it's a whole bunch of stuff that normal users would
never care about, but may be useful for debugging.  This clearly fits.

I also think that having a path down is something that shouldn't just
blip by once in the logs.  It's something that often requires the
sysadmin to intervene. I could see limitting it to, say, only happen
on every tenth pass through the checker loop, so that these messages
don't clog up the logs so bad. But since there is the option to set the
verbosity to 1 to avoid this, I think that printing the path down
messages repeatedly is useful.

-Ben

>
> Signed-off-by: Charlie Brady <charlieb@budge.apana.org.au>
>
> --- multipath-tools-0.4.7.rhel5.13/multipathd/main.c	2009-06-25 13:32:57.248455000 -0400
> +++ mezzanine_patched_multipath-tools-0.4.7.rhel5.13/multipathd/main.c	2009-06-25 13:32:12.968639000 -0400
> @@ -1041,7 +1041,6 @@
>  					enable_group(pp);
>  			}
>  			else if (newstate == PATH_UP || newstate == PATH_GHOST) {
> -				LOG_MSG(4, checker_message(&pp->checker));
>  				/*
>  				 * double the next check delay.
>  				 * max at conf->max_checkint
> @@ -1055,8 +1054,6 @@
>  				condlog(4, "%s: delay next check %is",
>  						pp->dev_t, pp->tick);
>  			}
> -			else if (newstate == PATH_DOWN)
> -				LOG_MSG(2, checker_message(&pp->checker));
>
>  			pp->state = newstate;
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel

  reply	other threads:[~2009-06-26 20:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25 17:50 [PATCH multipath-tools-0.4.7.rhel5.13 1/1] multipathd excessive path checker logging Charlie Brady
2009-06-26 20:50 ` Benjamin Marzinski [this message]
2009-06-26 23:54   ` Chandra Seetharaman
2009-06-27  1:39   ` Konrad Rzeszutek
2009-07-03 19:39     ` Charlie Brady
2009-06-29  6:19   ` Hannes Reinecke
2009-07-03 16:46 ` Unstable isci path and confusing logging Charlie Brady
2009-07-03 17:07   ` Charlie Brady
2009-07-03 17:14   ` Charlie Brady
2009-07-03 17:23     ` Charlie Brady

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090626205057.GL3172@ether.msp.redhat.com \
    --to=bmarzins@redhat.com \
    --cc=dm-devel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.