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
_______________________________________________
linux-lvm mailing list
linux-lvm@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
