linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <heinzm@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm2 raid volumes
Date: Wed, 3 Aug 2016 15:10:00 +0200	[thread overview]
Message-ID: <c5f4003c-f3ea-1aac-1727-d14ba3281d13@redhat.com> (raw)
In-Reply-To: <CAEMJtDsvR-70bVC2E=aMGoA1nR_ReqW-jVELTjmJyQDY+xzXnw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2867 bytes --]



On 08/03/2016 12:49 AM, Steve Dainard wrote:
> Hello,
>
> What are the methods for checking/monitoring a RAID LV?

Hi Stev,

see dmeventd (device-mapper monitoring daemon) and read lvm.conf WRT 
raid_fault_policy.

dmeventd provides warn or allocate mode allowing to either just warn 
about a RAID DataLV
or MetaLV failure or actively repair such failures. You'll find related 
messages in the system log.

>
> The Cpy%Sync field seems promising here:
>
> # lvs
>   LV    VG           Attr       LSize   Pool Origin Data%  Meta%  Move 
> Log Cpy%Sync Convert
>   raid1 test         rwi-aor--- 100.00m                  100.00
>   raid6 test         rwi-aor--- 108.00m                  100.00

The Cyp%Sync field tells you about the resynchronization progress, i.e. 
the initial mirroring of
all data blocks in a raid1/10 or the initial calculation and storing of 
parity blocks in raid4/5/6.

It should display a percentage value as in:

# lvs -o+devices iscsi
   LV   VG          Attr       LSize   Pool Origin Data%  Meta%  Move 
Log Cpy%Sync Convert Devices
   r    iscsi rwi-a-r--- 4.00t 0.03 
r_rimage_0(0),r_rimage_1(0),r_rimage_2(0),r_rimage_3(0),r_rimage_4(0),r_rimage_5(0)

Do you have a clean installation?
Try reinstalling lvm2 and device-mapper\*

>
> # pvs
>   PV         VG           Fmt  Attr PSize    PFree
>   /dev/vdb   test         lvm2 a--  1020.00m 876.00m
>   /dev/vdc   test         lvm2 a--  1020.00m 876.00m
>   /dev/vdd   test         lvm2 a--  1020.00m 980.00m
>   /dev/vde   test         lvm2 a--  1020.00m 980.00m
>   /dev/vdf   test         lvm2 a--  1020.00m 980.00m
>
> But testing in a VM by removing a disk does not change the output of lvs:
>
> # pvs
>   WARNING: Device for PV S5xFZ7-mLaH-GNQP-ujWh-Zbkt-Ww3u-J0aKUJ not 
> found or rejected by a filter.
>   PV             VG           Fmt  Attr PSize    PFree
>   /dev/vdb       test         lvm2 a--  1020.00m 876.00m
>   /dev/vdc       test         lvm2 a--  1020.00m 876.00m
>   /dev/vdd       test         lvm2 a--  1020.00m 980.00m
>   /dev/vde       test         lvm2 a--  1020.00m 980.00m
>   unknown device test         lvm2 a-m  1020.00m 980.00m
>
> # lvs
>   WARNING: Device for PV S5xFZ7-mLaH-GNQP-ujWh-Zbkt-Ww3u-J0aKUJ not 
> found or rejected by a filter.
>   LV    VG           Attr       LSize   Pool Origin Data%  Meta%  Move 
> Log Cpy%Sync Convert
>   raid1 test         rwi-aor--- 100.00m                  100.00
>   raid6 test         rwi-aor-p- 108.00m                  100.00
>
>
> My end goal is to write a nagios check to monitor for disk failures.

You may want to start with the Nagios checkvolmanager plugin...

Heinz

>
> Thanks,
> Steve
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


[-- Attachment #2: Type: text/html, Size: 6797 bytes --]

  reply	other threads:[~2016-08-03 13:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02 22:49 [linux-lvm] lvm2 raid volumes Steve Dainard
2016-08-03 13:10 ` Heinz Mauelshagen [this message]
2016-08-15 13:38   ` Xen
2016-09-16 14:13     ` Heinz Mauelshagen
2016-09-16 15:03       ` Xen

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=c5f4003c-f3ea-1aac-1727-d14ba3281d13@redhat.com \
    --to=heinzm@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).