From: ajs124 <linux-lvm@ajs124.de>
To: David Teigland <teigland@redhat.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] raidintegrity on non top level LVs
Date: Wed, 3 Aug 2022 23:14:26 +0200 [thread overview]
Message-ID: <20220803231426.4bc948e3@desk> (raw)
In-Reply-To: <20220803151554.GA28867@redhat.com>
On Wed, 3 Aug 2022 10:15:54 -0500
David Teigland <teigland@redhat.com> wrote:
> On Tue, Aug 02, 2022 at 04:27:53PM +0200, ajs124 wrote:
> > Hi,
> >
> > I've been wondering. Why does lvconvert not allow me to add raid
> > integrity to LVs that are not top level?
> > It only says "Integrity can only be added to top level raid LV."
> >
> > Skimming the commit that added this [1] did not provide me with
> > an answer, so I thought I'd ask here.
>
> Hi, good question, I think it was just an effort to limit the scope of the
> feature initially. Over time we can possibly expand the scope after
> seeing how things were working technically, and the experience of users.
> I'm curious to know what configuration you're trying, and if you have any
> experience using raid+integrity otherwise.
>
> Dave
Hi,
we're using a thin pool on top of two raid lvs for thinpool metadata
and data and I tried adding integrity to that.
We don't have much experience with raid+integrity, just a handful of
systems, which have been running fine. They're not particularly
performance critical and we don't have much data on how exactly they
behave.
The reason why I started looking into this again is because I observed
some mismatched sectors on a host, where all drives seem fine and I'd
like to have integrity to maybe figure out if any of the drives are
actually faulty.
ajs124
_______________________________________________
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/
prev parent reply other threads:[~2022-08-04 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 14:27 [linux-lvm] raidintegrity on non top level LVs ajs124
2022-08-03 15:15 ` David Teigland
2022-08-03 21:14 ` ajs124 [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=20220803231426.4bc948e3@desk \
--to=linux-lvm@ajs124.de \
--cc=linux-lvm@redhat.com \
--cc=teigland@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 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.