Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8084943 | emb-9 | Brian Burkhalter | P4 | Resolved | Fixed | team |
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
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
- backported by
-
JDK-8084943 (fs) Re-enable ability to fsync() on directories even though read()s on those directories may fail.
- Resolved
- relates to
-
JDK-8066915 (fs) Files.newByteChannel opens directories for cases where subsequent reads may fail
- Closed
-
JDK-8080589 (fs) FileChannel.force should use fcntl(F_FULLFSYNC) instead of fsync on OS X
- Closed
-
JDK-8080235 (fs) Provide ability to flush all modified buffered data to a permanent storage device
- Open