Sitsofe Wheeler

I don't think it's fair for the fio project to carry a "here's how direct I/O performs on filesystem X with configuration Y" compatibility table for (Linux) filesystems, especially given...

Labelling this one up as patcheswelcome because internally we don't have the manpower to get around to this one.

@fwin : This might have been fixed by a6eaf6c9101cd3f2895376944e6425a43613dbf6 - do you still see this problem with the latest fio releases?

Looks like this is still a problem. With fio 2.13 a file with 100 million I/Os to replay uses up enough memory on a 4GByte system to cause an OOM....

This is semi-addressed by https://github.com/axboe/fio/commit/98e7161cda6a1f5b0cbd8979c261db8eb3a4ab72 but it won't work for blktrace files - only fio's own iolog format...

@ipvirg Does everything work when you run a client and a server on the same machine and you use localhost/127.0.0.1?

(additionally can you include the contents of `fioconfig_64k_seq.fio` here?)

My faint memory is that fio's server mode needed `fork()` (which Windows doesn't do) and I'm not aware that has changed... Ah here we go: https://www.spinics.net/lists/fio/msg02565.html . Implementing a thread...

https://www.spinics.net/lists/fio/msg05248.html mentions the same `timeout on cmd PROBE` messages and in https://www.spinics.net/lists/fio/msg05262.html Jens replies: > Windows doesn't support fork(), and the fio server implementation was written to use processes. It...

Hi @MoranSimchi, Are the devices you're playing back on the same as those that the trace was recorded on?