<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Hello Kotresh,</div><div><br></div><div>Yes, the fd was still open for larger files. I could verify this with a 500MiB file and some smaller files. After a specific time only the fd for the 500MiB was up and the file still had no signature, for the smaller files there were no fds and they already had a signature. I don't know the reason for this. Maybe the client still keep th fd open? I opened a bug for this: <br></div><div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1685023">https://bugzilla.redhat.com/show_bug.cgi?id=1685023</a><br></div><div><br></div><div>Regards</div><div>David<br></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Am Fr., 1. März 2019 um 18:29 Uhr schrieb Kotresh Hiremath Ravishankar <<a href="mailto:khiremat@redhat.com">khiremat@redhat.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Interesting observation! But as discussed in the thread bitrot signing processes depends 2 min timeout (by default) after last fd closes. It doesn't have any co-relation with the size of the file.</div><div>Did you happen to verify that the fd was still open for large files for some reason?</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 1, 2019 at 1:19 PM David Spisla <<a href="mailto:spisla80@gmail.com" target="_blank">spisla80@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hello folks,</div><div><br></div><div>I did some observations concerning the bitrot daemon. It seems to be that the bitrot signer is signing files depending on file size. I copied files with different sizes into a volume and I was wonderung because the files get their signature not the same time (I keep the expiry time default with 120). Here are some examples:</div><div><br></div><div>
300 KB file ~2-3 m <br>
70 MB file ~ 40 m <br>
115 MB file ~ 1 Sh</div><div>800 MB file ~ 4,5 h</div><div><br></div><div>What is the expected behaviour here?</div><div>Why does it take so long to sign a 800MB file? <br></div><div>What about 500GB or 1TB?</div><div>Is there a way to speed up the sign process?<br></div><div><br></div><div>My ambition is to understand this observation</div><div><br></div><div>Regards</div><div>David Spisla<br></div></div>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-devel</a></blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail-m_-5896676527512337293gmail_signature"><div dir="ltr"><div>Thanks and Regards,<br></div>Kotresh H R<br></div></div>
</blockquote></div>