<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 29, 2016 at 7:51 PM, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
When NFS-Ganesha does an UNLINK of a filename on an inode, it does a<br>
follow-up check to see if the inode has been deleted or if there are<br>
still other filenames linked (like hardlinks) to it.<br>
<br>
Users are getting confused about the errors that are logged by RPC, DHT<br>
and AFR. The file is missing (which is often perfectly expected from a<br>
NFS-Ganesha point of view) and this causes a flood of messages.<br>
<br>
>From <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1328581#c5" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>show_bug.cgi?id=1328581#c5</a> :<br>
<br>
> If we reduce the log level for<br>
> client-rpc-fops.c:2974:<wbr>client3_3_lookup_cbk there would be the<br>
> following entries left:<br>
><br>
> 2x dht-helper.c:1179:dht_<wbr>migration_complete_check_task<br>
> 2x afr-read-txn.c:250:afr_read_<wbr>txn<br>
><br>
> it would reduce the logging for this non-error with 10 out of 14<br>
> messages. We need to know from the AFR and DHT team if these messages<br>
> are sufficient for them to identify potential issues.<br></blockquote><div><br>Updated the bug from the perspective of AFR as well: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1328581#c12">https://bugzilla.redhat.com/show_bug.cgi?id=1328581#c12</a><br><br>"I am not sure how an inode which is not in split-brain is linked as 'no read-subvolumes' case. That is something to debug."<br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Thanks,<br>
Niels<br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</div></div>