-
Enhancement
-
Resolution: Unresolved
-
P3
-
None
-
Cause Known
This issue follows from a change in undocumented behavior introduced by the JDK 9 fix of JDK-8066915. Previously in order to sync data to a directory, a FileChannel was opened in READ mode and then FileChannel.force() was invoked to flush modified in-state buffers and possibly metadata to the storage device. This behavior was however undocumented and not intended to be supported as for example a read() on the same directory FileChannel is unsupported and would provoke an exception.
The intent of this issue is to provide an alternate means to effect the desired behavior of force() within the bounds of the specification. This might call for new field definitions or new methods.
The intent of this issue is to provide an alternate means to effect the desired behavior of force() within the bounds of the specification. This might call for new field definitions or new methods.
- relates to
-
JDK-8080629 (fs) Re-enable ability to fsync() on directories even though read()s on those directories may fail.
- Resolved
-
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