On Tue, Sep 09, 2008 at 01:55:46PM +0900, Alex Lee wrote:
> I been seeing something that looks like IB timeout errors lately after
> upgrading to 1.6.5.1 using the supplied ofed kernel drivers.
> ..
> Sep 9 00:25:31 lustre-oss-4-1 kernel: LustreError:
> 13228:0:(o2iblnd_cb.c:2874:kiblnd_chec
Alex Lee wrote:
>> These timeouts can happen on a busy network. If they are frequent, you
>> should increase obd_timeout.
>> cliffw
>>
>>
>
> obd_timeout is already set at 300secs which I think is pretty long...
> Does the error message means it timed out after using up all 300sec
> waittime a
> These timeouts can happen on a busy network. If they are frequent, you
> should increase obd_timeout.
> cliffw
>
>
obd_timeout is already set at 300secs which I think is pretty long...
Does the error message means it timed out after using up all 300sec
waittime and then additional 20secs?
Alex Lee wrote:
> I been seeing something that looks like IB timeout errors lately after
> upgrading to 1.6.5.1 using the supplied ofed kernel drivers.
>
> From what I can tell there hasnt been any real network issues that was
> apparent. Are these errors just typical if the network is busy?
C
I been seeing something that looks like IB timeout errors lately after
upgrading to 1.6.5.1 using the supplied ofed kernel drivers.
From what I can tell there hasnt been any real network issues that was
apparent. Are these errors just typical if the network is busy?
Heres from MDS:
Sep 8 16:
