In certain situations, smaller files will report I/O errors when accessed from NFS using Gluster NFS. With our settings, files up to 170M could report this in some cases. It was not a consistent failure.
Disbling the NFS performance I/O cache seemed to work around the instances of the problem observed for non-sharded volumes.
Research showed that gluster NFS is relying on an errno return value of EINVAL to detect EOF and set is_eof. However, in some paths this value was not retained or was reset to zero.
This change passes the errno along so it can be used by gluster NFS. We found the issue in the shard xlator and the io-cache xlator.
In certain situations, smaller files will report I/O errors when accessed from NFS using Gluster NFS. With our settings, files up to 170M could report this in some cases. It was not a consistent failure.
Disbling the NFS performance I/O cache seemed to work around the instances of the problem observed for non-sharded volumes.
Research showed that gluster NFS is relying on an errno return value of EINVAL to detect EOF and set is_eof. However, in some paths this value was not retained or was reset to zero.
This change passes the errno along so it can be used by gluster NFS. We found the issue in the shard xlator and the io-cache xlator.