From: Gionatan Danti <g.danti@assyoma.it>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] lvmcache with vdo - inconsistent block size
Date: Mon, 14 Sep 2020 23:44:23 +0200 [thread overview]
Message-ID: <3f51904f43c45f8c1259f1b050402358@assyoma.it> (raw)
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?
Thanks.
[1] Output from lsblk -t:
[root@singularity dev]# lsblk -t | cut -c1-73
NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC
LOG-SEC
sda 0 512 0 512 512
├─sda1 0 512 0 512 512
├─sda2 0 512 0 512 512
│ ├─system-root 0 512 0 512 512
│ └─system-swap 0 512 0 512 512
├─sda3 0 512 0 512 512
└─sda4 0 512 0 512 512
sdb 0 512 0 512 512
└─sdb 0 512 0 512 512
└─md200 0 524288 1048576 512 512
└─vdo1 0 4096 4096 4096 4096
├─vg_kvm-thinpool_tmeta 0 4096 4096 4096 4096
│ └─vg_kvm-thinpool-tpool 0 1048576 1048576 4096 4096
│ ├─vg_kvm-thinpool 0 1048576 1048576 4096 4096
│ └─vg_kvm-thinvol 0 1048576 1048576 4096 4096
└─vg_kvm-thinpool_tdata 0 4096 4096 4096 4096
└─vg_kvm-thinpool-tpool 0 1048576 1048576 4096 4096
├─vg_kvm-thinpool 0 1048576 1048576 4096 4096
└─vg_kvm-thinvol 0 1048576 1048576 4096 4096
sdc 0 512 0 512 512
└─sdc 0 512 0 512 512
└─md200 0 524288 1048576 512 512
└─vdo1 0 4096 4096 4096 4096
├─vg_kvm-thinpool_tmeta 0 4096 4096 4096 4096
│ └─vg_kvm-thinpool-tpool 0 1048576 1048576 4096 4096
│ ├─vg_kvm-thinpool 0 1048576 1048576 4096 4096
│ └─vg_kvm-thinvol 0 1048576 1048576 4096 4096
└─vg_kvm-thinpool_tdata 0 4096 4096 4096 4096
└─vg_kvm-thinpool-tpool 0 1048576 1048576 4096 4096
├─vg_kvm-thinpool 0 1048576 1048576 4096 4096
└─vg_kvm-thinvol 0 1048576 1048576 4096 4096
sdd 0 512 0 512 512
└─sdd 0 512 0 512 512
└─md200 0 524288 1048576 512 512
└─vdo1 0 4096 4096 4096 4096
├─vg_kvm-thinpool_tmeta 0 4096 4096 4096 4096
│ └─vg_kvm-thinpool-tpool 0 1048576 1048576 4096 4096
│ ├─vg_kvm-thinpool 0 1048576 1048576 4096 4096
│ └─vg_kvm-thinvol 0 1048576 1048576 4096 4096
└─vg_kvm-thinpool_tdata 0 4096 4096 4096 4096
└─vg_kvm-thinpool-tpool 0 1048576 1048576 4096 4096
├─vg_kvm-thinpool 0 1048576 1048576 4096 4096
└─vg_kvm-thinvol 0 1048576 1048576 4096 4096
sde 0 512 0 512 512
└─sde 0 512 0 512 512
└─md200 0 524288 1048576 512 512
└─vdo1 0 4096 4096 4096 4096
├─vg_kvm-thinpool_tmeta 0 4096 4096 4096 4096
│ └─vg_kvm-thinpool-tpool 0 1048576 1048576 4096 4096
│ ├─vg_kvm-thinpool 0 1048576 1048576 4096 4096
│ └─vg_kvm-thinvol 0 1048576 1048576 4096 4096
└─vg_kvm-thinpool_tdata 0 4096 4096 4096 4096
└─vg_kvm-thinpool-tpool 0 1048576 1048576 4096 4096
├─vg_kvm-thinpool 0 1048576 1048576 4096 4096
└─vg_kvm-thinvol 0 1048576 1048576 4096 4096
[2] [root@singularity dev]# vgextend vg_kvm /dev/sda4
Devices have inconsistent logical block sizes (4096 and 512).
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next reply other threads:[~2020-09-14 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 21:44 Gionatan Danti [this message]
2020-09-15 18:34 ` [linux-lvm] lvmcache with vdo - inconsistent block size Zdenek Kabelac
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=3f51904f43c45f8c1259f1b050402358@assyoma.it \
--to=g.danti@assyoma.it \
--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 NNTP newsgroup(s).