From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: References: <20010715180752.B7993@weta.f00f.org> From: Juan Quintela In-Reply-To: <20010715180752.B7993@weta.f00f.org> Date: 16 Jul 2001 20:31:57 -0400 Message-ID: MIME-Version: 1.0 Subject: [linux-lvm] Re: [PATCH] 64 bit scsi read/write Sender: linux-lvm-admin@sistina.com Errors-To: linux-lvm-admin@sistina.com Reply-To: linux-lvm@sistina.com List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Chris Wedgwood Cc: John Alvord , Daniel Phillips , 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 >>>>> "chris" == Chris Wedgwood writes: chris> On Sat, Jul 14, 2001 at 11:05:36PM -0700, John Alvord wrote: chris> In the IBM solution to this (1977-78, VM/CMS) the critical data was chris> written at the begining and the end of the block. If the two data items chris> didn't match then the block was rejected. chris> Neat. chris> Simple and effective. Presumably you can also checksum the block, and chris> check that. There is the rumor (I can't confirm that), that you need checksums, that some disks are able to write well the beginning & the end of the sector and put garbage in the middle in the case of problems. I have never been able to reproduce that errors, but .... Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy