Yep, this issue was spotted on another system in the last week, it's due to a fallocate() option not being supported by some kernels on some file systems. To workaround this, I added two layers of emulation in an abstraction layer to fallocate to resolve this:
commit 74c7f40b63ec0c0e9321480d372b76b437188a23
Author: Colin Ian King <email address hidden>
Date: Thu Feb 9 10:17:06 2017 +0000
shim: add emulation for failed fallocate(2)
Add two layers of workarounds for fallocate() failures: firstly
try zero mode flags if mode causes EOPNOTSUPP, secondly, use
slow emulation mode if fallocate with zero flag fails with EOPNOTSUPP.
Can you try the latest release, V0.07.20 that has that fix.
Hi Jeff,
Yep, this issue was spotted on another system in the last week, it's due to a fallocate() option not being supported by some kernels on some file systems. To workaround this, I added two layers of emulation in an abstraction layer to fallocate to resolve this:
commit 74c7f40b63ec0c0 e9321480d372b76 b437188a23
Author: Colin Ian King <email address hidden>
Date: Thu Feb 9 10:17:06 2017 +0000
shim: add emulation for failed fallocate(2)
Add two layers of workarounds for fallocate() failures: firstly
try zero mode flags if mode causes EOPNOTSUPP, secondly, use
slow emulation mode if fallocate with zero flag fails with EOPNOTSUPP.
Can you try the latest release, V0.07.20 that has that fix.
Colin