All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gionatan Danti <g.danti@assyoma.it>
To: Zdenek Kabelac <zkabelac@redhat.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvmcache with vdo - inconsistent block size
Date: Thu, 17 Sep 2020 23:41:29 +0200	[thread overview]
Message-ID: <7725f4635181d25b6dda227b7e7a39cb@assyoma.it> (raw)
In-Reply-To: <4f98430e-f6eb-b7b7-d1b0-f54ad07361de@redhat.com>

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

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.

> So if you already hit some problem - feel free to open upstream BZ for
> this issue.

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

-- 
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8

  reply	other threads:[~2020-09-17 21:41 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 [this message]
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=7725f4635181d25b6dda227b7e7a39cb@assyoma.it \
    --to=g.danti@assyoma.it \
    --cc=linux-lvm@redhat.com \
    --cc=zkabelac@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.