Linux-LVM Archive mirror
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: Arvid Picciani <aep@exys.org>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] is lvmraid 1 thinpool with integrity safe?
Date: Tue, 11 Apr 2023 08:15:16 -0500	[thread overview]
Message-ID: <20230411131516.GA27598@redhat.com> (raw)
In-Reply-To: <CACD9L=A9i6QFzXtnQh6e3=gD9u6cy3VJAtCEaf1WsoCU_eE3kQ@mail.gmail.com>

On Sun, Apr 09, 2023 at 02:21:50PM +0200, Arvid Picciani wrote:
> Hi,
> 
> doing some performance tests i noticed that lvmraid + integrity + thinpool
> outperforms zfs z1 by 5x while offering the same features. (snapshots,
> integrity)
> 
> Is this somehow unsafe or how come it is so unpopular?
> 
> lvcreate --type raid1 --mirrors 1 --size '100M' loop --name loopmeta
> --raidintegritymode journal
> lvcreate --type raid1 --mirrors 1 --size '700M' loop --name loopdata
> --raidintegritymode journal

Hi, that command does not actually enable integrity.  You need to include
the option "--raidintegrity y".  (lvcreate should perhaps warn you about
setting raidintegritymode when you've not enabled integrity.)

> lvconvert --type thin-pool --poolmetadata loop/loopmeta loop/loop

We do not currently permit raid+integrity to be used for a thin pool.  It
should be enabled in a coming release.

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/


      parent reply	other threads:[~2023-04-11 13:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-09 12:21 [linux-lvm] is lvmraid 1 thinpool with integrity safe? Arvid Picciani
2023-04-11  9:15 ` Gionatan Danti
2023-04-11 13:15 ` David Teigland [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=20230411131516.GA27598@redhat.com \
    --to=teigland@redhat.com \
    --cc=aep@exys.org \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).