Thanks for you tips, I would have a try as you said to disable the NOOP.
I had make a XFS file system on the LUN at the Initiator side .
Finally, I catch the sync_cache command was issued by XFS log
infrastructure actually. When I replace the XFS with EXT2 that dmesg
error don`t appear anymore
On 05/20/2016 04:14 PM, Mike Christie wrote:
> On 05/20/2016 11:39 AM, The Lee-Man wrote:
>> Hi:
>>
>> It seems like your backend is getting busy and not replying in time when
>> it gets very busy. You can disable the NOOP, or you can lengthen its
>> interval, I believe.
>>
>> If there is a bug,
On 05/20/2016 11:39 AM, The Lee-Man wrote:
> Hi:
>
> It seems like your backend is getting busy and not replying in time when
> it gets very busy. You can disable the NOOP, or you can lengthen its
> interval, I believe.
>
> If there is a bug, it would be in the kernel target subsystem. Have you
Hi:
It seems like your backend is getting busy and not replying in time when it
gets very busy. You can disable the NOOP, or you can lengthen its interval,
I believe.
If there is a bug, it would be in the kernel target subsystem. Have you
tried the target-devel @ vger kernel mailing list?
On
Hi everyone:
I create a target using fileio as the backend storage on ARM64 server. The
initiator reported some errors showed bellow while perform iozone test.
[178444.145679] connection14:0: ping timeout of 5 secs expired, recv
timeout 5, last rx 4339462894, last ping 4339464146, now
