archive mirror
 help / color / mirror / Atom feed
From: Erwin van Londen <>
To: LVM general discussion and development <>
Subject: Re: [linux-lvm] move dm-integrity metadata to another PV
Date: Mon, 05 Apr 2021 10:59:46 +1000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20210404181856.6hevvwxwyflsm373@helios>

[-- Attachment #1.1: Type: text/plain, Size: 1160 bytes --]

Maybe an idea to add a cache volume to the LV?? Not 100% sure if this
works but would be nice to try.

On Sun, 2021-04-04 at 20:18 +0200, Sebastian Bachmann wrote:
> Hello,
> I played around with the new dm-integrity integration in lvm.
> Unfortunately, it
> is very slow, as the checksums has to be written and read on - which
> is the
> price to pay obviously.
> I thought that it might be a good idea to move the metadata to a fast
> disk,
> i.e., a SSD, however that is not possible and I get an error message
> on pvmove:
> # pvmove -n r10_int_rimage_0_imeta /dev/sdd /dev/sda2
>   Unable to pvmove device used for raid with integrity.
> I could not find a reason why this should not be done in theory, thus
> I guess
> that this is simply not supported by LVM right now?
> Or is there another reason why you should keep the metadata always on
> the same
> device?
> Best,
> Sebastian
> _______________________________________________
> linux-lvm mailing list
> read the LVM HOW-TO at

[-- Attachment #1.2: Type: text/html, Size: 1795 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

linux-lvm mailing list
read the LVM HOW-TO at

  reply	other threads:[~2021-04-06 11:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-04 18:18 [linux-lvm] move dm-integrity metadata to another PV Sebastian Bachmann
2021-04-05  0:59 ` Erwin van Londen [this message]
2021-04-05 15:08 ` David Teigland
2021-04-05 15:40   ` Sebastian Bachmann

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).