From: Juan Quintela <quintela@mandrakesoft.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: John Alvord <jalvo@mbay.net>,
Daniel Phillips <phillips@bonn-fries.net>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <andrewm@uow.edu.au>,
Andreas Dilger <adilger@turbolinux.com>,
"Albert D. Cahalan" <acahalan@cs.uml.edu>,
Ben LaHaise <bcrl@redhat.com>,
Ragnar Kjxrstad <kernel@ragnark.vestdata.no>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mike@bigstorage.com, kevin@bigstorage.com, linux-lvm@sistina.com
Subject: [linux-lvm] Re: [PATCH] 64 bit scsi read/write
Date: 16 Jul 2001 20:31:57 -0400 [thread overview]
Message-ID: <m2ofqk5rb6.fsf@mandrakesoft.com> (raw)
In-Reply-To: <20010715180752.B7993@weta.f00f.org>
>>>>> "chris" == Chris Wedgwood <cw@f00f.org> 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
next prev parent reply other threads:[~2001-07-17 0:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010703065312.J4841@vestdata.no>
[not found] ` <Pine.LNX.4.33.0107032211120.30968-100000@toomuch.toronto.redhat.com>
2001-07-05 6:34 ` [linux-lvm] Re: [PATCH] 64 bit scsi read/write Ragnar Kjørstad
2001-07-05 7:35 ` Ben LaHaise
2001-07-05 16:46 ` AJ Lewis
2001-07-05 17:09 ` Eric M. Hopper
2001-07-10 13:45 ` Heinz J. Mauelshagen
2001-07-13 18:20 ` Albert D. Cahalan
2001-07-13 20:41 ` Andreas Dilger
2001-07-13 21:14 ` Alan Cox
2001-07-14 3:23 ` Andrew Morton
2001-07-14 8:45 ` Alan Cox
2001-07-14 13:54 ` Steven Lembark
2001-07-14 17:33 ` Jonathan Lundell
[not found] ` <20010715160247.I7624@weta.f00f.org>
2001-07-15 5:46 ` Jonathan Lundell
[not found] ` <20010715025001.B6722@weta.f00f.org>
2001-07-14 15:41 ` Jonathan Lundell
2001-07-14 20:11 ` Daniel Phillips
2001-07-15 1:21 ` Andrew Morton
2001-07-15 1:53 ` Daniel Phillips
[not found] ` <20010715153607.A7624@weta.f00f.org>
2001-07-15 6:05 ` John Alvord
[not found] ` <20010715180752.B7993@weta.f00f.org>
2001-07-15 13:16 ` Ken Hirsch
2001-07-15 22:14 ` Daniel Phillips
2001-07-17 0:31 ` Juan Quintela [this message]
2001-07-15 13:44 ` Daniel Phillips
[not found] ` <20010716023911.A10576@weta.f00f.org>
2001-07-15 15:06 ` Jonathan Lundell
[not found] ` <20010716032220.B10635@weta.f00f.org>
2001-07-15 17:44 ` Jonathan Lundell
2001-07-15 17:47 ` Justin T. Gibbs
2001-07-15 23:14 ` Rod Van Meter
[not found] ` <20010716205633.G11938@weta.f00f.org>
2001-07-16 13:19 ` Daniel Phillips
2001-07-16 14:26 ` Heinz J. Mauelshagen
2001-07-15 15:32 ` Alan Cox
[not found] <20010714090703.B5737@weta.f00f.org>
2001-07-13 22:04 ` Andreas Dilger
2001-07-14 0:49 ` Jonathan Lundell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ofqk5rb6.fsf@mandrakesoft.com \
--to=quintela@mandrakesoft.com \
--cc=acahalan@cs.uml.edu \
--cc=adilger@turbolinux.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrewm@uow.edu.au \
--cc=bcrl@redhat.com \
--cc=cw@f00f.org \
--cc=jalvo@mbay.net \
--cc=kernel@ragnark.vestdata.no \
--cc=kevin@bigstorage.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@sistina.com \
--cc=mike@bigstorage.com \
--cc=phillips@bonn-fries.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox