You mentioned that you're getting messages like this: > [94930.551379] qla2xxx [0000:02:00.0]-801c:13: Abort command issued nexus=13:0:1 -- 1 2002. As previously mentioned if your disk controller is aborting commands you need to find out why - it's not really a userspace generated issue. Until you know why that's happening all that will happen is that the abort will bubble all the way back up to whatever sent the I/O as an error. On Tue, 14 Aug 2018 at 05:23, آرش خاوری راد <arash.khavary@xxxxxxxxx> wrote: > > I check in deep in terminal when FIO is running i got this error: > > fio: io_u error on file /dev/sdg: Input/output error: write > offset=241038262272, buflen=4194304 > fio: io_u error on file /dev/sdg: Input/output error: write > offset=241042456576, buflen=4194304 > fio: io_u error on file /dev/sdg: Input/output error: write > offset=246167896064, buflen=4194304 > fio: io_u error on file /dev/sdg: Input/output error: write > offset=246172090368, buflen=4194304 > > > > 2018-08-07 5:28 GMT+00:00 Sitsofe Wheeler <sitsofe@xxxxxxxxx>: > > On 7 August 2018 at 04:57, آرش خاوری راد <arash.khavary@xxxxxxxxx> wrote: > >> > >> Unfortunately my problem not solved, I change Blocksize but got arror again > >> > >> fio: io_u error on file /dev/sdc: Input/output error: write > >> offset=1677721600, buflen=4194304 > > > > Is there anything suspicious in dmesg? If you cut the number of > > sections down to one does it still happen? Is it alway against the > > same disk? > > > > -- > > Sitsofe | http://sucs.org/~sits/ > > > > -- > با عرض احترام خاوری راد - آرش -- Sitsofe | http://sucs.org/~sits/
