All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Janne Heß" <janne+lvm@hess.ooo>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: "Janne Heß" <janne+lvm@hess.ooo>
Subject: Re: [linux-lvm] RAID-less parity?
Date: Thu, 30 Jul 2020 22:49:37 +0200	[thread overview]
Message-ID: <1k1FUf-0008Bw-6B@mx1.helsinki.tools> (raw)
In-Reply-To: <20200714160556.GA16281@redhat.com>

Hi,
Am Dienstag, 14. Juli 2020 18:05 CEST, schrieb David Teigland <teigland@redhat.com>: 
 
> On Mon, Jul 13, 2020 at 04:34:52PM +0200, Janne Heß wrote:
> > However some of my systems are single-disk systems. For those, RAIDs are
> > not possible so I was thinking if LVM has some support for single-PV
> > setups with parity on the same PV.
> 
> Hi,
> 
> We didn't include integrity+linear because we didn't see much value in it,
> since it would require going to backups in case of an integrity failure.
> 
> > While this is probably a niche feature right now, I can see other
> > projects like Stratis benefit from the integrity checks provided by
> > dm-integrity (and dm-crypt in the future) to detect (and thanks to
> > parity fix) bit rots.
> 
> dm-integrity will detect but not fix bit rot.

This is where I see a benefit from having some parity on the LVM level.
With dm-integrity spotting bit-rots and reporting errors to LVM, LVM
can recover the blocks with parity information.
This recovery procedure would give more feature parity to ZFS
which I'm currently migrating from for a LVM-based solution.

> 
> > So is there any way to get a parity setup with the current state of LVM?
> > I was thinking of a RAID-4 with one PV but the current tooling (more
> > specifically lvcreate) doesn't let me do that.
> 
> It's not currently possible.  We had an implementation for this we could
> bring back if there is enough interest, so we'd like to hear more about
> how this would be useful for you and others.

I think this would be beneficial for a lot of users since it allows spotting
and correcting bit-rots which is currently not possible other than using
ZFS or RAID as far as I know.
> 
> Thanks,
> Dave
> 
> _______________________________________________
> 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/
> 
 
 Thanks,
Janne

      parent reply	other threads:[~2020-07-30 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 14:34 [linux-lvm] RAID-less parity? Janne Heß
2020-07-14 15:15 ` Gionatan Danti
2020-07-14 16:05 ` David Teigland
2020-07-14 20:32   ` Gionatan Danti
2020-07-30 20:49   ` Janne Heß [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=1k1FUf-0008Bw-6B@mx1.helsinki.tools \
    --to=janne+lvm@hess.ooo \
    --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 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.