All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: "Martin Dünkelmann" <nc-duenkekl3@netcologne.de>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Questions about monitoring, scrubbing & checking a LVM RAID5
Date: Thu, 29 Jul 2021 09:59:46 -0500	[thread overview]
Message-ID: <20210729145946.GA22305@redhat.com> (raw)
In-Reply-To: <630e7a16-5305-9319-52e2-8c45da6e9e27@netcologne.de>

On Wed, Jul 28, 2021 at 11:50:56PM +0200, Martin Dünkelmann wrote:
> Dear LVM2-People,
> 
> I made a native RAID5 via LVM on 3 SSDs without mdadm, since LVM2 can do it
> natively.
> 
> But I got confused about how to easily monitor it (send emails about errors,
> since it's a remove server) and how to check, repair and scrub the RAID5.
> 
> Using:
> "sudo lvchange --syncaction check cryptdata_raid5/home" (same for repair)
> results in
> 
> Command on LV cryptdata_raid5/home does not accept LV type linear.
> Command not permitted on LV cryptdata_raid5/home.

It works for me, so it could be a fixed bug.  Check that the LV is really
raid5: lvs -o segtype cryptdata_raid5/home

> Does that mean LVM2 doesn't fully support native RAID5 and I should format
> everything and set up a mdadm raid5?
> Because mdadm has scrubbing and email reports according to the mdadm.conf.

Right, mdadm does much more.

Dave

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


  reply	other threads:[~2021-07-29 15:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 21:50 [linux-lvm] Questions about monitoring, scrubbing & checking a LVM RAID5 Martin Dünkelmann
2021-07-29 14:59 ` David Teigland [this message]
2021-07-29 15:53   ` Martin Dünkelmann

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=20210729145946.GA22305@redhat.com \
    --to=teigland@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=nc-duenkekl3@netcologne.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.