On 1 August 2018 at 07:39, Alireza Haghdoost <haghdoost@xxxxxxxxx> wrote: > Your jobs step on the foot of each other. You can’t write with multiple > process on the same LBA of a LUN on the same time. That is why you get error > 5 because one thread is writting an LBA and another thread modify if at the > same time. In this case either one can get unknown result. I agree with part of this statement (unknown result in the LBA) but I'm doubtful it would cause an error message of "I/O error". Disks definitely do accept simultaneous write I/Os against the same LBA but the problem becomes that in most cases the end result as to which data the LBA will contain is undefined. It's not illegal (in the sense that nothing prevents and nothing will error) it's just bad from a data integrity perspective (and since this wasn't a verify job...). -- Sitsofe | http://sucs.org/~sits/ -- 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
