archive mirror
 help / color / mirror / Atom feed
From: Sebastian Bachmann <>
Subject: [linux-lvm] move dm-integrity metadata to another PV
Date: Sun, 4 Apr 2021 20:18:56 +0200	[thread overview]
Message-ID: <20210404181856.6hevvwxwyflsm373@helios> (raw)


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


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

             reply	other threads:[~2021-04-04 18:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-04 18:18 Sebastian Bachmann [this message]
2021-04-05  0:59 ` [linux-lvm] move dm-integrity metadata to another PV Erwin van Londen
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 \
    --in-reply-to=20210404181856.6hevvwxwyflsm373@helios \ \ \

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