Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 15 Jul 2001 00:03:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 15 Jul 2001 00:02:54 -0400 Received: from weta.f00f.org ([203.167.249.89]:50563 "HELO weta.f00f.org") by vger.kernel.org with SMTP id ; Sun, 15 Jul 2001 00:02:44 -0400 Date: Sun, 15 Jul 2001 16:02:47 +1200 From: Chris Wedgwood To: Jonathan Lundell Cc: Alan Cox , Andrew Morton , Andreas Dilger , "Albert D. Cahalan" , Ben LaHaise , Ragnar Kjxrstad , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, mike@bigstorage.com, kevin@bigstorage.com, linux-lvm@sistina.com Subject: Re: [PATCH] 64 bit scsi read/write Message-ID: <20010715160247.I7624@weta.f00f.org> In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.18i X-No-Archive: Yes Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jul 14, 2001 at 10:33:44AM -0700, Jonathan Lundell wrote: What's worse, though the spec is not explicit on this point, it appears that the write cache is lost on a SCSI reset, which is typically used by drivers for last-resort error recovery. And of course a SCSI bus reset affects all the drives on the bus, not just the offending one. Doesn't SCSI have a notion of write barriers? Even if this is required, the above still works because for anything requiring a barrier, you wait of a positive SYNCHRONIZE CACHE --cw - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/