From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm2 low space handling
Date: Wed, 08 Oct 2014 11:40:03 +0200 [thread overview]
Message-ID: <54350673.8010202@redhat.com> (raw)
In-Reply-To: <5434562C.6020307@mglug.de>
Dne 7.10.2014 v 23:07 Oliver Rath napsal(a):
> Hi list,
>
> how can I get some email, if a thin pool runs full? On my syslog i found
> the following messages:
>
>
> Oct 7 21:29:25 dmicn20 kernel: [1115276.145019] device-mapper: thin:
> 252:13: reached low water mark for metadata device: sending event.
> Oct 7 21:29:33 dmicn20 kernel: [1115284.693816] device-mapper: thin:
> 252:13: reached low water mark for metadata device: sending event.
> Oct 7 21:29:35 dmicn20 kernel: [1115286.086837] device-mapper: thin:
> 252:13: reached low water mark for metadata device: sending event.
> Oct 7 21:29:36 dmicn20 kernel: [1115287.369534] device-mapper: thin:
> 252:13: reached low water mark for metadata device: sending event.
> Oct 7 21:29:55 dmicn20 kernel: [1115306.290745] device-mapper: thin:
> 252:13: reached low water mark for metadata device: sending event.
> ...
>
> How can i find these messages?
Have you enabled thin threshold in lvm.conf?
thin_pool_autoextend_threshold = 70
thin_pool_autoextend_percent = 20
Currently there is not yet better policy support for filled thin pool devices.
And yes - you need to trap syslog messages if you want monitoring for filled
pool - there is no other support yet (i.e. dbus messaging)
Zdenek
prev parent reply other threads:[~2014-10-08 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 21:07 [linux-lvm] lvm2 low space handling Oliver Rath
2014-10-08 9:40 ` Zdenek Kabelac [this message]
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=54350673.8010202@redhat.com \
--to=zkabelac@redhat.com \
--cc=linux-lvm@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;
as well as URLs for NNTP newsgroup(s).