From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Reed Subject: Re: [PATCH] Make scsi error recovery play nice with devices blocked by transport Date: Fri, 13 Jan 2006 13:50:05 -0600 Message-ID: <43C8046D.5010804@sgi.com> References: <43A35498.6030903@sgi.com> <43B2B77B.20602@emulex.com> <43BEE23E.8040707@sgi.com> <43C27ABC.2020504@emulex.com> <1136821157.3364.11.camel@mulgrave> <43C7FFB4.5000801@sgi.com> <20060113193837.GB5668@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from omx2-ext.sgi.com ([192.48.171.19]:57048 "EHLO omx2.sgi.com") by vger.kernel.org with ESMTP id S1422865AbWAMTuN (ORCPT ); Fri, 13 Jan 2006 14:50:13 -0500 In-Reply-To: <20060113193837.GB5668@lst.de> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Christoph Hellwig Cc: James Bottomley , James.Smart@Emulex.Com, linux-scsi@vger.kernel.org, Jeremy Higdon , Gary Hagensen Christoph Hellwig wrote: > On Fri, Jan 13, 2006 at 01:29:56PM -0600, Michael Reed wrote: >>I'm planning on working on this once the fusion fc_transport code finally >>makes it in. What do you see as a deadline for code addressing this problem? >> >>Perhaps someone else already has something to address this in progress? >>It's a significant issue with our fibre channel customers. > > There's not at all. Sunday is feature deadline for 2.6.16, but we'll > happily accept everything good for 2.6.17. OTOH this probably falls > into fixes that can go in after -rc1 anyway. > I was hoping that was the case. It's pretty broken as it is today. Mike