JDK-8080629 : (fs) Re-enable ability to fsync() on directories even though read()s on those directories may fail.
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.nio
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux,os_x,solaris
  • Submitted: 2015-05-18
  • Updated: 2015-06-04
  • Resolved: 2015-05-19
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b66Fixed
Related Reports
Relates :  
JDK-8066915 - (fs) Files.newByteChannel opens directories for cases where subsequent reads may fail
Relates :  
JDK-8080235 - (fs) Provide ability to flush all modified buffered data to a permanent storage device
Relates :  
JDK-8080589 - (fs) FileChannel.force should use fcntl(F_FULLFSYNC) instead of fsync on OS X
Description
This issue is in effect to track the reversion of the patch which resolved JDK-8066915. This patch caused some serious problems for developers as have been outlined in these threads of discussion:

1) January 2015 - http://mail.openjdk.java.net/pipermail/nio-dev/2015-January/002979.html
2) May 2015 - http://mail.openjdk.java.net/pipermail/nio-dev/2015-May/003140.html
Comments
Revert patch that resolved JDK-8066915.
18-05-2015
Review thread - http://mail.openjdk.java.net/pipermail/nio-dev/2015-May/003159.html.
18-05-2015