Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 15 Jul 2001 01:47:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 15 Jul 2001 01:47:37 -0400 Received: from geos.coastside.net ([207.213.212.4]:24821 "EHLO geos.coastside.net") by vger.kernel.org with ESMTP id ; Sun, 15 Jul 2001 01:47:23 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <20010715160247.I7624@weta.f00f.org> In-Reply-To: <20010715160247.I7624@weta.f00f.org> Date: Sat, 14 Jul 2001 22:46:20 -0700 To: Chris Wedgwood From: Jonathan Lundell Subject: Re: [PATCH] 64 bit scsi read/write 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 Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org At 4:02 PM +1200 2001-07-15, Chris Wedgwood wrote: >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 for a positive SYNCHRONIZE CACHE Sure, if you keep all your write buffers around until then, so you can re-write if the sync fails. And if you don't crash in the meantime. -- /Jonathan Lundell. - 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/