viliam-durina opened a new issue, #14334: URL: https://github.com/apache/lucene/issues/14334
### Description According to [this answer](https://stackoverflow.com/a/50158433/952135), calling `fsync` after the file descriptor is closed gives no guarantees about what's persistent on disk. This is exactly what Lucene does: the `sync` method is on `Directory`, the implementation opens the file, calls `FileChannel.force()`, and closes it. The `sync` method, according to this, should have been on `IndexOutput`, and it should be called before the file is closed after writing. Perhaps it's the cause of the unresolved issue #10906. I'm not experiencing this issue myself and have no reproducer, I've realized it by reading about `fsync`. ### Version and environment details Lucene 10.1 on Linux, Java 21 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
