From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Christie Subject: Re: Fw: [Bugme-new] [Bug 3651] New: dell poweredge 4600 aacraidPERC 3/Di Container goes offline Date: Wed, 24 Nov 2004 12:29:01 -0800 Message-ID: <41A4EF0D.7020507@us.ibm.com> References: <60807403EABEB443939A5A7AA8A7458B694FA8@otce2k01.adaptec.com> <20041124130904.GA12830@infradead.org> <41A4A1B3.5070106@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from e35.co.us.ibm.com ([32.97.110.133]:31215 "EHLO e35.co.us.ibm.com") by vger.kernel.org with ESMTP id S262831AbUKXUXe (ORCPT ); Wed, 24 Nov 2004 15:23:34 -0500 Received: from westrelay01.boulder.ibm.com (westrelay01.boulder.ibm.com [9.17.195.10]) by e35.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id iAOKNXQf095010 for ; Wed, 24 Nov 2004 15:23:33 -0500 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by westrelay01.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id iAOKNW1Q210806 for ; Wed, 24 Nov 2004 13:23:32 -0700 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id iAOKNVk6020622 for ; Wed, 24 Nov 2004 13:23:32 -0700 In-Reply-To: <41A4A1B3.5070106@us.ibm.com> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: brking@us.ibm.com Cc: Christoph Hellwig , "Salyzyn, Mark" , Ryan Anderson , linux-scsi@vger.kernel.org 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?