Hey folks, Just wanted to raise awareness about a I/O issue that seems to be affecting some Linux Kernal releases that were listed as STABLE, causing corruption when using the ext4 filesystem with direct I/O. I don't have time to get a great understanding of the full scope of the issue, what versions are affected, etc, I just want to get this in front of the project. I am disappointed that this might negatively affect our ability to leverage direct I/O for both the commitlog (recently merged) and SSTables (potentially a future use case), since users won't be able to discern between a bug we ship and one that we hit as a result of our filesystem choices.
I think it might be worth putting a note in our docs and in the config to warn the user to ensure they're not affected, and we may even want to consider hiding this feature if the blast radius is significant enough that users would be affected. https://lwn.net/Articles/954285/ Jon
