Hi David,
Thanks for raising the bug. But from the above validation, it's clear that
bitrot is not directly involved. Bitrot waits for last fd to be closed. We
will have to investigate the reason for fd not being closed for large files.
Thanks,
Kotresh HR
On Mon, Mar 4, 2019 at 3:13 PM David
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.
Did you happen to verify that the fd was still open for large files for
some reason?
On Fri, Mar
Hello folks,
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
