[dm-devel] [PATCH] multipath: don't print so many add map messages
Christophe Varoqui
christophe.varoqui at gmail.com
Sat Nov 12 10:17:35 UTC 2011
On ven., 2011-11-11 at 23:12 -0600, Benjamin Marzinski wrote:
> Whenever a dm device gets a change uevent, multipathd prints an add map
> message. This can get confusing for users, so change that message to
> not print at the default log level, and add a new message that only
> prints if multipathd will actually try to add a map
>
Applied.
> Signed-off-by: Benjamin Marzinski <bmarzins at redhat.com>
> ---
> multipathd/main.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> Index: multipath-tools-111111/multipathd/main.c
> ===================================================================
> --- multipath-tools-111111.orig/multipathd/main.c
> +++ multipath-tools-111111/multipathd/main.c
> @@ -232,7 +232,7 @@ uev_add_map (struct uevent * uev, struct
> char *alias;
> int major = -1, minor = -1, rc;
>
> - condlog(2, "%s: add map (uevent)", uev->kernel);
> + condlog(3, "%s: add map (uevent)", uev->kernel);
> alias = uevent_get_dm_name(uev);
> if (!alias) {
> condlog(3, "%s: No DM_NAME in uevent", uev->kernel);
> @@ -280,6 +280,7 @@ ev_add_map (char * dev, char * alias, st
> }
> return 0;
> }
> + condlog(2, "%s: adding map", alias);
>
> /*
> * now we can register the map
More information about the dm-devel
mailing list