linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	Gionatan Danti <g.danti@assyoma.it>
Subject: Re: [linux-lvm] lvmcache with vdo - inconsistent block size
Date: Tue, 15 Sep 2020 20:34:56 +0200	[thread overview]
Message-ID: <5070f4fa-81ad-9c9a-b0a7-8d5463ea09d3@redhat.com> (raw)
In-Reply-To: <3f51904f43c45f8c1259f1b050402358@assyoma.it>

Dne 14. 09. 20 v 23:44 Gionatan Danti napsal(a):
> Hi all,
> I am testing lvmcache with VDO and I have issue with devices block size.
> 
> The big & slow VDO device is on top of a 4-disk MD RAID 10 device (itself on 
> top of dm-integrity). Over the VDO device I created a thinpool and a thinvol 
> [1]. When adding the cache device to the volume group via vgextend, I get an 
> error stating "Devices have inconsistent logical block sizes (4096 and 512)." [2]
> 
> Now, I know why the error shows and what i means. However, I don't know how to 
> force the cache device to act as a 4k sector device, and/if this is really 
> required to cache a VDO device.
> 
> My current workaround is to set VDO with --emulate512=enabled, but this can be 
> suboptimal and it is not recommended.
> 
> Any idea on what I am doing wrong?

Hi

LVM currently does not support mixing devices of different sector sizes within
a single VG as it brings lot of troubles we have not yet clear vision what
to do with all of them.

Also this combination of provisioned devices is not advised - since you are 
combining 2 kind of devices on top of each other and it can be a big problem
to solve recovery case.

On lvm2 side we do not allow to use 'VDO LV' as backend for thin-pool device.

So ATM it's on a user to solve all the possible scenarios that may appear on
such device stack.

Zdenek

  reply	other threads:[~2020-09-15 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14 21:44 Gionatan Danti
2020-09-15 18:34 ` Zdenek Kabelac [this message]
2020-09-15 22:32   ` Gionatan Danti
2020-09-17 19:27     ` Zdenek Kabelac
2020-09-17 21:41       ` Gionatan Danti
2020-09-17 21:46         ` Zdenek Kabelac

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=5070f4fa-81ad-9c9a-b0a7-8d5463ea09d3@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=g.danti@assyoma.it \
    --cc=linux-lvm@redhat.com \
    --subject='Re: [linux-lvm] lvmcache with vdo - inconsistent block size' \
    /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

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