Recent Java 9 commit (e5b66323ae45) breaks fsync on directory

[Brian Burkhalter]

We have revised our approach to this (pair or trio of) problem(s). The following sequence of actions is proposed.

1. Revert the patch which fixed https://bugs.openjdk.java.net/browse/JDK-8066915, (fs) Files.newByteChannel opens directories for cases where subsequent reads may fail, which instigated the present situation. I will file and post the link to a new Issue for this.

2. Work on a fix for https://bugs.openjdk.java.net/browse/JDK-8080589, (fc) FileChannel.force should use fcntl(F_FULLFSYNC) instead of fsync on OS X.

3. Work on a zero to minimal impact fix for https://bugs.openjdk.java.net/browse/JDK-8080235, (fs) Provide ability to flush all modified buffered data to a permanent storage device.

Hopefully the foregoing plan of record shall be to everyone’s satisfaction and will converge to an eventual mutually acceptable, logical solution.

Thanks,

Brian

On May 16, 2015, at 9:48 AM, Robert Muir <rcmuir at gmail.com> wrote:

> Is it really not possible to revert the change that broke all this?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/nio-dev/attachments/20150518/92ae3c3c/attachment.html>