<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Claudio,</p>
<p>I made a test with NFS mount with nfsvers=4.1 and CentOS 7 as NFS
client (our Netapp already have NFS 4.1 enabled) but the problem
is still present.</p>
<p>More, I don't like to switch to NFS 4 because is statefull, NFS
v3 is stateless and for example during maintanace or upgrade of
NFS server clients haven't problems, the reboot of Netapp is
trasparent.</p>
<p>I don't think the problem is related to Netapp, I see the same
error in a setup of a customer based on Google Cloud (Ubuntu as
Dovecot and NFS client and Google Cloud NFS volume as storage).</p>
<p>In my case I'm using LDA for local delivery of emails so I hope
that swithcing to LMTP I will resolve the issue but I'm not use
since others users said that they are aready using LMTP.</p>
<p>I don't know why on old Linux distro works and recents distro
have the issue ...<br>
</p>
<div class="moz-cite-prefix">Il 19/01/21 20:21, Claudio Cuqui ha
scritto:<br>
</div>
<blockquote type="cite"
cite="mid:CAD-pyVWaZHea7w-d0NLeRXu_x=MQF4rKgJoTVAtZgDp8M+9Uug@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>It's a long shot......but I would try to use nfsvers=4.1 in
the nfs mount option (instead of nfsvers=3) - if your netapp
supports it - with a newer kernel - 4.14-stable or 4.19-stable
(if possible). The reason for that, is a nasty bug found in
linux nfs client with older kernels...<br>
</div>
<div><br>
</div>
<div><a
href="https://about.gitlab.com/blog/2018/11/14/how-we-spent-two-weeks-hunting-an-nfs-bug/"
moz-do-not-send="true">https://about.gitlab.com/blog/2018/11/14/how-we-spent-two-weeks-hunting-an-nfs-bug/</a></div>
<div><br>
</div>
<div>Hope this helps...</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Claudio<br>
</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Em qua., 13 de jan. de 2021 às
12:18, Maciej Milaszewski <<a
href="mailto:maciej.milaszewski@iq.pl"
moz-do-not-send="true">maciej.milaszewski@iq.pl</a>>
escreveu:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi<br>
I have been trying resolve my problem with dovecot for a few
days and I<br>
dont have idea....<br>
<br>
My environment is: dovecot director+5 dovecot guest<br>
<br>
dovecot-2.2.36.4 from source<br>
Linux 3.16.0-11-amd64<br>
storage via nfs (NetApp)<br>
<br>
all works fine but when I update OS from debian 8 (kernel
3.16.x) to<br>
debian 9 (kernel 4.9.x ) sometimes I get random in logs:<br>
Broken dovecot-uidlist<br>
<br>
examle:<br>
Error: Broken file<br>
/vmail2/po/pollygraf.xxx_pg_pollygraf/Maildir/dovecot-uidlist
line 88:<br>
Invalid data:<br>
<br>
(for random users - sometimes 10 error in day per node, some
times more)<br>
<br>
File looks ok<br>
<br>
But if I change kernel to 3.16.x problem with "Broken file<br>
dovecot-uidlist" - not exists<br>
if turn to 4.9 or 5.x - problem exists<br>
<br>
I have storage via nfs with opions:<br>
rw,sec=sys,noexec,noatime,tcp,hard,rsize=65536,wsize=65536,intr,nordirplus,nfsvers=3,tcp,actimeo=120<br>
I tested with "nocto" or without "nocto" - nothing changes
......<br>
<br>
nfs options in node:<br>
mmap_disable = yes<br>
mail_fsync = always<br>
<br>
I bet the configuration is correct and I wonder why the
problem occurs<br>
with other kernels<br>
3.x.x - ok<br>
4.x - not ok<br>
<br>
I check and user who have problem did not connect to another
node in<br>
this time<br>
<br>
I dont have idea why problem exists on the kernel 4.x but not
in 3.x<br>
<br>
<br>
</blockquote>
</div>
</blockquote>
<pre class="moz-signature" cols="72">--
Alessio Cecchi
Postmaster @ <a class="moz-txt-link-freetext" href="http://www.qboxmail.it">http://www.qboxmail.it</a>
<a class="moz-txt-link-freetext" href="https://www.linkedin.com/in/alessice">https://www.linkedin.com/in/alessice</a></pre>
</body>
</html>