Skip to contentSkip to conversation

lvm2 low space handling

linux-lvm Oliver Rath 2 participants 2 messages Oct 7, 2014 – Oct 8, 2014

lore
Share & tools
lore
#0 lore raw

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?

Tfh!
Oliver

#1 lore raw

Dne 7.10.2014 v 23:07 Oliver Rath napsal(a):

Quoted 15 lines

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:
Quoted 4 lines

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