From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Subject: Re: [linux-lvm] Removing lvmcache fails
Date: Mon, 21 Sep 2020 14:53:39 +0200 [thread overview]
Message-ID: <c6499a9a-1e69-9502-85b5-b62bb5a4771b@redhat.com> (raw)
In-Reply-To: <2072153092.4261300.1600682482754.JavaMail.zimbra@karlsbakk.net>
Dne 21. 09. 20 v 12:01 Roy Sigurd Karlsbakk napsal(a):
>> Dne 21. 09. 20 v 10:51 Roy Sigurd Karlsbakk napsal(a):
>>> Hi all
>>>
>> However since you have 'writethrough' cache mode - it should be possible to
>> use 'lvconvert --uncache --force'
>
> # lvconvert --uncache --force data/data
> Unknown feature in status: 8 2484/262144 128 819198/819200 57470386 35323243 19987362 9940326 0 0 1 3 metadata2 writethrough no_discard_passdown 2 migration_threshold 2048 smq 0 rw -
> Flushing 1 blocks for cache data/data.
> Unknown feature in status: 8 2484/262144 128 819198/819200 57439248 35307947 19981793 9938992 0 0 1 3 metadata2 writethrough no_discard_passdown 2 migration_threshold 2048 cleaner 0 rw -
> Flushing 1 blocks for cache data/data.
> Unknown feature in status: 8 2484/262144 128 819198/819200 57439248 35307947 19981793 9938992 0 0 1 3 metadata2 writethrough no_discard_passdown 2 migration_threshold 2048 cleaner 0 rw -
> (et cetera et cetera ad infinitum)
>
>> But I'm somehow confused how you can have any dirty blocks in this case ??
>
> So am I
>
>> lvm2 2.03.02 version was somewhat experimental release - so I've recommend
>> something newer - which will also properly parse newer status output from
>> newer kernel dm-cache module.
>
> Well, that's weird - debian is usually rather conservative on its packages in a stable release. Are you sure?
>
> I also updated to a backported kernel 5.7 without any change.
Hi
Please can you open upstream BZ here:
https://bugzilla.redhat.com/enter_bug.cgi?product=LVM%20and%20device-mapper
List all the info - i.e. package versions (yep even .debs), kernel versions
lvmdump archive.
I can probably easily 'hand-make' lvm2 metadata for you for 'vgcfgrestore' -
but I'd like to track this case and create some reproducer for this issue so
we can handle case were the cache cannot be cleared.
Regards
Zdenek
next prev parent reply other threads:[~2020-09-21 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 8:51 [linux-lvm] Removing lvmcache fails Roy Sigurd Karlsbakk
2020-09-21 9:47 ` Zdenek Kabelac
2020-09-21 10:01 ` Roy Sigurd Karlsbakk
2020-09-21 12:53 ` Zdenek Kabelac [this message]
2020-09-21 13:24 ` Roy Sigurd Karlsbakk
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=c6499a9a-1e69-9502-85b5-b62bb5a4771b@redhat.com \
--to=zkabelac@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=roy@karlsbakk.net \
/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).