On Fri, Jan 18 2013, brian arb wrote: > adding the option --verify_backlog=1024 resolved my issue. > On a side note how would one determine what the optimum number is for this > option? It's easier if you know the internals... The version you are running will store some metadata for each block written, for verification purposes. Standard install is 80 bytes per block. So if you have a 2TB disk and use 4K IO sizes, the memory required runs into the gigabytes. Quite unfortunate, really, will be fixed up shortly. In any case, with a backlog of just 1024, you wont use more than 80KB memory for verifies. So you could easily size it larger. I'd improve the option documentation, but I think it's better to just improve fio to not require the stored meta data to be able to verify. It will be in the 2.0.14 release. -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
