Re: Fw: [Bugme-new] [Bug 3651] New: dell poweredge 4600 aacraidPERC 3/Di Container goes offline

[Brian King <brking@us.ibm.com>]

Mike Christie wrote:
> Brian King wrote:
> 
>>
>>
>> Christoph Hellwig wrote:
>>
>>> On Wed, Nov 24, 2004 at 07:59:04AM -0500, Salyzyn, Mark wrote:
>>>
>>>> I dropped Andrew Morton from the direct mail recipients.
>>>>
>>>> Thanks, made the change in my branch of the code. This adjustment will
>>>> probably never be submitted to MarkH since I use it only for debugging
>>>> purposes. However, would it be nice if the global scsi timeout could be
>>>> `user' adjustable?
>>>>
>>>> Not that I advocate it as readily accessible, since any storage device
>>>> that takes longer than ten seconds is in `trouble', and any timeout
>>>> longer than two minutes will no doubt cause servers to go offline on 
>>>> the
>>>> internet. Its purpose is only for troubleshooting.
>>>
>>>
>>>
>>>
>>> Yes, it would probably be nice to have a writeable timeout attribute for
>>> the scsi device.  Care to submit a patch?
>>
>>
>>
>> This already exists today.
>>
> 
> Is there any problems with that attr and drivers not being able to handle
> the timeouts someone sets in sysfs. I mean if in my slave_configure I set
> 60 secs becuase for some reason my HW takes this long no matter what, 
> someone
> can reset this to 5 or 1 sec and there are is chance for the lld to 
> override
> this if it is invalid. Is this just one of those things where we say
> only touch the timeout if you know what you are doing, or is it that the 
> lld
> should not have that power, or sometihng else?

Well, personally, I think this is a case of only touch the timeout if you know
what you are doing, but the infrastructure is certainly there for the LLD to
override the timeout attribute and do whatever policing might need to be done.



-- 
Brian King
eServer Storage I/O
IBM Linux Technology Center