[lvm-devel] lvmcache in writeback mode gets stuck flushing dirty blocks
Zdenek Kabelac
zkabelac at redhat.com
Tue Jul 30 08:21:30 UTC 2019
Dne 30. 07. 19 v 6:58 Lakshmi Narasimhan Sundararajan napsal(a):
> Hi Team,
>
> A very good day to all.
>
>
> I am using lvmcache in writeback mode. When there are dirty blocks still in
> the lv, and if needs to be destroyed or flushed, then
>
> It seems to me that there are some conditions under which the dirty data flush
> gets stuck forever.
>
> As an example:
>
> root at pdc4-sm35:~# lvremove -f pwx0/pool
>
> 367 blocks must still be flushed.
>
> 367 blocks must still be flushed.
>
> 367 blocks must still be flushed.
> I am running these version:
>
> root at pdc4-sm35:~# lvm version
>
> LVM version: 2.02.133(2) (2015-10-30)
>
> I filed one here myself, https://github.com/lvmteam/lvm2/issues/22, trying to
> understand from you experts where we are on this?
>
> I would sincerely appreciate your help in understanding the state of this
> issue in more detail.
Hi
Yep you are using very old version of lvm2 - there is already year 2019 - and
in the initial releases of lvm2 with writeback cache support (as you happen to
still use these days) there was a problem that uncaching was not switching to
writethrough mode (and this was not the only one)
Please consider to use way newer lvm2 & kernel.
Regards
Zdenek
More information about the lvm-devel
mailing list