<html xmlns:v="urn:schemas-microsoft-com:vml" 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)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1308583225;
mso-list-type:hybrid;
mso-list-template-ids:675469452 134807567 134807577 134807579 134807567 134807577 134807579 134807567 134807577 134807579;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Force -f is improper in situations when NFS server is gone.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>I have node intranet-test2 with nfs mount and nas-sync-test2 with NFS server and export resources.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>I made following experiment:<o:p></o:p></span></p><ol style='margin-top:0cm' start=1 type=1><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'><span style='mso-fareast-language:EN-US'>Paused the VM running nas-sync-test2 so cluster lost the member<o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'><span style='mso-fareast-language:EN-US'>Executed umount -f /folder and it displayed error umount.nfs4: /folder: device is busy<o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'><span style='mso-fareast-language:EN-US'>Executed umount -f -l /folder and all fine<o:p></o:p></span></li></ol><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Reference: <a href="https://askubuntu.com/questions/292043/how-to-unmount-nfs-when-server-is-gone">https://askubuntu.com/questions/292043/how-to-unmount-nfs-when-server-is-gone</a><o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Is it possible to add the lazy -l option to the umount ?<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> Miro Igov <miro.igov@pharmya.com> <br><b>Sent:</b> 11 April 2023 21:47<br><b>To:</b> Cluster Labs - All topics related to open-source clustering welcomed <users@clusterlabs.org><br><b>Subject:</b> Re: [ClusterLabs] NFS mount fails to stop if NFS server is lost<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>What about umount -f -l ?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div id=ms-outlook-mobile-signature><div id=mail-editor-reference-message-container><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="98%" align=center></div><div id=divRplyFwdMsg><p class=MsoNormal><strong><span style='font-family:"Calibri",sans-serif'>From:</span></strong> Users <<a href="mailto:users-bounces@clusterlabs.org">users-bounces@clusterlabs.org</a>> on behalf of Andrei Borzenkov <<a href="mailto:arvidjaar@gmail.com">arvidjaar@gmail.com</a>><br><strong><span style='font-family:"Calibri",sans-serif'>Sent:</span></strong> Tuesday, April 11, 2023, 20:26<br><strong><span style='font-family:"Calibri",sans-serif'>To:</span></strong> <a href="mailto:users@clusterlabs.org">users@clusterlabs.org</a> <<a href="mailto:users@clusterlabs.org">users@clusterlabs.org</a>><br><strong><span style='font-family:"Calibri",sans-serif'>Subject:</span></strong> Re: [ClusterLabs] NFS mount fails to stop if NFS server is lost<o:p></o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'><br>On 11.04.2023 17:35, Miro Igov wrote:<br>> Hello,<br>> <br>> I have a node nas-sync-test1 with NFS server and NFS export running and<br>> another node intranet-test1 with data_1 fs mount:<br>> <br>> <br>> <br>> primitive data_1 Filesystem \<br>> <br>> params device="nas-sync-test1:/home/pharmya/NAS" fstype=nfs<br>> options=v4 directory="/data/synology/pharmya_office/NAS_Sync/NAS" \<br>> <br>> op monitor interval=10s<br>> <br>> <br>> <br>> Disconnecting nas-sync-test1 from the network shows it's state as UNCLEAN<br>> and pacemaker fences it.<br>> <br>> Then it tries to stop data_1 but it shows timeout error.<br>> <br>> <br>> <br>> I know unmounting of NFS mount when NFS server is gone requires force. Is<br>> there such option in Filesystem RA ?<br>> <br><br>It does it unconditionally from the very beginning<br><br># For networked filesystems, there's merit in trying -f:<br>case "$FSTYPE" in<br>nfs4|nfs|efs|cifs|smbfs) umount_force="-f" ;;<br>esac<br><br>But IIRC it is not enough (at least, not always) - so the trick is to <br>setup the same IP address as server had. It could be an alias on a local <br>client interface, does not matter. I suppose client gets stuck somewhere <br>below application layer and having IP resets TCP connection allowing it <br>to proceed.<br><br>I certainly had to do it in the past, and simple "umount -f" did not work.<br>_______________________________________________<br>Manage your subscription:<br><a href="https://lists.clusterlabs.org/mailman/listinfo/users">https://lists.clusterlabs.org/mailman/listinfo/users</a><br><br>ClusterLabs home: <a href="https://www.clusterlabs.org/">https://www.clusterlabs.org/</a><br><br><o:p></o:p></p></div></div></div>
<br><table id="pharmya_gdpr_container" border="0" cellspacing="0" cellpadding="0" width="100%">
<tr>
<td width="600">
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr>
<td style="border-top: 2px solid #8C8C8C; text-align:justify;">
<img src="cid:3f12576c67d7ece83cf8eacd2f7265c3"
class="replace_cid" alt="GDPR Logo" width="126"
height="50" align="left" style="margin-right:5px;"/>
<span style="font-size:10pt;
font-family: Segoe, 'Segoe UI', 'DejaVu Sans', 'Trebuchet MS', Verdana, sans-serif;"
class="gdpr_text">
This message has been sent as a part of discussion between PHARMYA
and the addressee whose name is specified above. Should you receive
this message by mistake, we would be most grateful if you informed
us that the message has been sent to you. In this case, we also ask
that you delete this message from your mailbox, and do not forward
it or any part of it to anyone else.<br>
Thank you for your cooperation and understanding.
</span>
</td>
</tr>
</table>
</td>
<td></td>
</table>
<br></body></html>