<div dir="ltr"><div dir="ltr"><div>Hello Amudhan,</div><div><br></div><div>What does exactly mean "it takes < 250KB/s"?<br></div><div>I figured out this discussion between you and Kotresh: <a href="https://lists.gluster.org/pipermail/gluster-users/2016-September/028354.html" target="_blank">https://lists.gluster.org/pipermail/gluster-users/2016-September/028354.html</a></div><div>Kotresh mentioned there that the problem is because for some files fd process are still up in the brick process list. Bitrot signer can only sign a file if the fd is closed.
And according to my observations it seems to be that as bigger a file is as longer the fd is still up. 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.<br></div><div><br></div><div>Does anybody know what is the reason for this? For me it looks loke a bug. <br></div><div><br></div><div>Regards</div><div>David<br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Am Fr., 1. März 2019 um 08:58 Uhr schrieb Amudhan P <<a href="mailto:amudhan83@gmail.com" target="_blank">amudhan83@gmail.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">Hi David,<div><br></div><div>I have also tested the bitrot signature process by default it takes < 250 KB/s.</div><div><br></div><div>regards</div><div>Amudhan P</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-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a></blockquote></div>
</blockquote></div>