Michel Machado

The logs show that you are writing and reading one file at a time. So my best guess is that `f3read` is getting the data from a cache. One needs...

Please do the test I mention above. The result may help us to understand the issue further. By the way, given that your script only tests the last written files,...

These drives are fine. The explanation for the super speed that motivated this thread is likely due to a cache in the hardware or the operating system.

If you do want to dig into this problem, you'll need to isolate the cause. For example, finding out if these drives produce the same effect on other machines. If...

I've pushed a patch in that might have solved this issue; for details see #102. Could you test the code in the repository on your problem?

Please ignore my previous comment, I wrongly conflated two unrelated issues.

A pull request to improve the information about Docker in the README, or another documentation file, is welcome. Thank you for your contribution, @gchenfc.

`f3brew` already writes and reads at the block level, see `make extra`.

Hi @Pfeil, The documentation is not gone. We have moved it to Read the Docs to enable anyone to contribute to it by issuing pull requests here on GitHub. While...

If you translate your effort of reading the code of F3 into improving the documentation, I'll be happy to merge your pull request. If the efforts of everyone that has...