Description of problem:
In the case of fsync fails with error, the posix_fsync in posix xlator does not correctly return the error code.
Version-Release number of selected component (if applicable):
The mainline, and 3.4, 3.5 and 3.6 branch are all affected.
Steps to Reproduce:
Seems like you know the issue, want to send a patch?
REVIEW: http://review.gluster.org/8398 (storage/posix: fix return value of posix_fsync on error) posted (#1) for review on master by Zhang Huan (email@example.com)
REVIEW: http://review.gluster.org/8398 (storage/posix: fix issue in posix_fsync) posted (#2) for review on master by Zhang Huan (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/8398 committed in master by Vijay Bellur (email@example.com)
Author: Zhang Huan <firstname.lastname@example.org>
Date: Fri Mar 7 11:08:47 2014 +0800
storage/posix: fix issue in posix_fsync
Fix the issue that posix_fsync does not correctly return and save
error code in op_errno when call to sys_fdatasync fails.
Signed-off-by: Zhang Huan <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Pranith Kumar Karampuri <email@example.com>
Reviewed-by: Santosh Pradhan <firstname.lastname@example.org>
Reviewed-by: Vijay Bellur <email@example.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.
glusterfs-3.7.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.