<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi Team,</p><p class=MsoNormal>A very good day to all.</p><p class=MsoNormal><br>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</p><p class=MsoNormal>It seems to me that there are some conditions under which the dirty data flush gets stuck forever.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As an example:</p><p class=MsoNormal>root@pdc4-sm35:~# lvremove -f pwx0/pool</p><p class=MsoNormal> 367 blocks must still be flushed.</p><p class=MsoNormal> 367 blocks must still be flushed.</p><p class=MsoNormal> 367 blocks must still be flushed.</p><p class=MsoNormal> 367 blocks must still be flushed.</p><p class=MsoNormal> 367 blocks must still be flushed.</p><p class=MsoNormal> 367 blocks must still be flushed.</p><p class=MsoNormal>^C</p><p class=MsoNormal>root@pdc4-sm35:~#</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I am running these version:</p><p class=MsoNormal>root@pdc4-sm35:~# lvm version</p><p class=MsoNormal> LVM version: 2.02.133(2) (2015-10-30)</p><p class=MsoNormal> Library version: 1.02.110 (2015-10-30)</p><p class=MsoNormal> Driver version: 4.34.0</p><p class=MsoNormal>root@pdc4-sm35:~#</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This issue seems old and reported multiple places. There have been some acknowledgement that this issue is resolved in 2.02.133, but still I see it. Also, I have seen some posts report it in 2.02.170+ as well (here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878441) (<span style='font-size:10.0pt;font-family:"Courier New";color:black;background:#FEFEFE'>Package: lvm2 Version: 2.02.173-1 Severity: normal)</span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I filed one here myself, <a href="https://github.com/lvmteam/lvm2/issues/22">https://github.com/lvmteam/lvm2/issues/22</a>, trying to understand from you experts where we are on this?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I would sincerely appreciate your help in understanding the state of this issue in more detail.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Best regards<br>LN</p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>