From: Christophe Varoqui <christophe.varoqui@free.fr>
To: daniel.keisling@austin.ppdi.com
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: Temporarily squelching multipathd errors
Date: Sat, 19 Jul 2008 10:27:50 +0200 [thread overview]
Message-ID: <1216456070.7364.4.camel@plop> (raw)
> Greetings,
>
> I perform SAN-based snapshots on OCFS2 and ext3 filesystems under
> dm-multipath. Before I snapshot the filesystem, I unmount and delete
> the previous night's snapshot LUNs. Doing so causes (correctly)
> multipathd to output the following errors:
>
> <snip>
> ...
> Jul 14 03:16:02 ausracdbd01 multipathd: mpath19: remaining active paths:
> 7
> Jul 14 03:16:02 ausracdbd01 multipathd: sdci: tur checker reports path
> is down
> Jul 14 03:16:02 ausracdbd01 kernel: device-mapper: multipath: Failing
> path 69:80.
> Jul 14 03:16:02 ausracdbd01 multipathd: sdco: tur checker reports path
> is down
> ....
> </snip>
>
> During this snapshot time, I would like to temporarily turn off the
> verbosity of multipathd. Is this possible? It's mostly an annoyance
> factor for me because our nightly centralized syslog scan picks up words
> like 'fail' and generates a report to the system administrators (which
> we then have to ignore for these messages).
>
Why not just remove the multipath from the multipathd topology before deleting the snapvol ?
multipathd -k"del map mpath19"
Regards,
cvaroqui
next reply other threads:[~2008-07-19 8:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 8:27 Christophe Varoqui [this message]
2008-10-30 15:48 ` Temporarily squelching multipathd errors Daniel Keisling
2008-10-30 16:15 ` Domenico Viggiani
2008-11-21 19:54 ` Daniel Keisling
2008-11-26 17:43 ` Konrad Rzeszutek
2009-01-16 20:59 ` Daniel Keisling
[not found] ` <65F9ACC78BD8304BAAEB817634C62D4C07441224@AUSMAIL01.americas.ppdi.local>
2009-01-16 21:28 ` Konrad Rzeszutek
2009-01-16 21:52 ` Daniel Keisling
2009-01-19 15:07 ` Konrad Rzeszutek
-- strict thread matches above, loose matches on Subject: below --
2008-07-18 18:48 Daniel Keisling
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=1216456070.7364.4.camel@plop \
--to=christophe.varoqui@free.fr \
--cc=daniel.keisling@austin.ppdi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox