archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <>
To: Gionatan Danti <>
Cc: LVM general discussion and development <>
Subject: Re: [linux-lvm] lvmcache with vdo - inconsistent block size
Date: Thu, 17 Sep 2020 23:46:26 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Dne 17. 09. 20 v 23:41 Gionatan Danti napsal(a):
> Il 2020-09-17 21:27 Zdenek Kabelac ha scritto:
>> You've most likely found the bug and this should be likely disable
>> (and enabled only with some force option).
> Hi Zdenek, I am not sure about what bug I found - can you be more explicit?
>> Problem is, when such device stack is used for XFS - where the
>> 'geometry' changes, but for some other it's not a big issue (i.e.
>> ext4).

XFS doesn't like when 4K device becomes 512b sector based.

> Again, I am not sure about what we are speaking - generic thinlvm over VDO, or 
> about the caching issue discussed before? Why this should be an issue for XFS 
> vs EXT4? From RH docs, I can see VDO + thinlvm + XFS as being fully supported.

Here you are using separate level of tooling - so you have separate dealing
with errors on each device with its own tooling.

lvm2 is not yet capable to handle this stack on its own.

> I'll do, but I first need to understand the core issue better.

Create XFS on 4K sector device - copy it on 512b and use it.


      reply	other threads:[~2020-09-17 21:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14 21:44 [linux-lvm] lvmcache with vdo - inconsistent block size Gionatan Danti
2020-09-15 18:34 ` 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 [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:

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