From: Jeff Garzik <jeff@garzik.org>
To: ric@emc.com
Cc: Theodore Tso <tytso@mit.edu>, Bryan Henderson <hbryan@us.ibm.com>,
Al Boldi <a1426z@gawab.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
David Chinner <dgc@sgi.com>,
linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
Daniel Phillips <phillips@google.com>,
Rik van Riel <riel@redhat.com>,
Valerie Henson <val.henson@gmail.com>
Subject: Re: [Patch] document ext3 requirements (was Re: [RFD] Incremental fsck)
Date: Fri, 18 Jan 2008 15:34:54 -0500 [thread overview]
Message-ID: <47910D6E.3070801@garzik.org> (raw)
In-Reply-To: <4790C50F.2080704@emc.com>
Ric Wheeler wrote:
> Theodore Tso wrote:
>> On Thu, Jan 17, 2008 at 04:31:48PM -0800, Bryan Henderson wrote:
>>> But I heard some years ago from a disk drive engineer that that is a
>>> myth just like the rotational energy thing. I added that to the
>>> discussion, but admitted that I haven't actually seen a disk drive
>>> write a partial sector.
>>
>> Well, it would be impossible or at least very hard to see that in
>> practice, right? My understanding is that drives do sector-level
>> checksums, so if there was a partially written sector, the checksum
>> would be bogus and the drive would return an error when you tried to
>> read from it.
>
> There is extensive per sector error correction on each sector written.
> What you would see in this case (or many, many other possible ways
> drives can corrupt media) is a "media error" on the next read.
Correct.
> You would never get back the partially written contents of that sector
> at the host.
Correct.
> Having our tools (fsck especially) be resilient in the face of media
> errors is really critical. Although I don't think the scenario of a
> partially written sector is common, media errors in general are common
> and can develop over time.
Agreed.
Jeff
next prev parent reply other threads:[~2008-01-18 20:35 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 21:22 [RFD] Incremental fsck Al Boldi
2008-01-08 21:31 ` Alan
2008-01-09 9:16 ` Andreas Dilger
2008-01-12 23:55 ` Daniel Phillips
2008-01-08 21:41 ` Rik van Riel
2008-01-09 4:40 ` Al Boldi
2008-01-09 7:45 ` Valerie Henson
2008-01-09 11:52 ` Al Boldi
2008-01-09 14:44 ` Rik van Riel
2008-01-10 13:26 ` Al Boldi
2008-01-12 14:51 ` Theodore Tso
2008-01-13 11:05 ` Al Boldi
2008-01-13 17:19 ` Pavel Machek
2008-01-13 17:41 ` Alan Cox
2008-01-15 20:16 ` [Patch] document ext3 requirements (was Re: [RFD] Incremental fsck) Pavel Machek
2008-01-15 21:43 ` David Chinner
2008-01-15 23:07 ` Pavel Machek
2008-01-15 23:44 ` Daniel Phillips
2008-01-16 0:15 ` Alan Cox
2008-01-16 1:24 ` Daniel Phillips
2008-01-16 1:36 ` Chris Mason
2008-01-17 20:54 ` Pavel Machek
2008-01-16 19:06 ` Bryan Henderson
2008-01-16 20:05 ` Alan Cox
2008-01-17 2:02 ` Daniel Phillips
2008-01-17 21:37 ` Bryan Henderson
2008-01-17 22:45 ` Theodore Tso
2008-01-17 22:58 ` Alan Cox
2008-01-17 23:18 ` Ric Wheeler
2008-01-18 0:31 ` Bryan Henderson
2008-01-18 14:23 ` Theodore Tso
2008-01-18 15:16 ` [Patch] document ext3 requirements (was Re: [RFD] Incrementalfsck) linux-os (Dick Johnson)
2008-01-19 14:53 ` Pavel Machek
2008-01-18 15:26 ` [Patch] document ext3 requirements (was Re: [RFD] Incremental fsck) Ric Wheeler
2008-01-18 20:34 ` Jeff Garzik [this message]
2008-01-18 22:35 ` Bryan Henderson
2008-01-18 15:08 ` H. Peter Anvin
2008-01-18 17:43 ` Bryan Henderson
2008-01-16 21:28 ` Eric Sandeen
2008-01-16 11:51 ` Pavel Machek
2008-01-16 12:20 ` Valdis.Kletnieks
2008-01-19 14:51 ` Pavel Machek
2008-01-16 16:38 ` Christoph Hellwig
2008-01-16 1:44 ` Daniel Phillips
2008-01-16 3:05 ` Rik van Riel
2008-01-17 7:38 ` Andreas Dilger
2008-01-16 11:49 ` Pavel Machek
2008-01-16 20:52 ` Valerie Henson
2008-01-17 12:29 ` Szabolcs Szakacsits
2008-01-17 22:51 ` Daniel Phillips
2008-01-15 1:04 ` [RFD] Incremental fsck Ric Wheeler
2008-01-14 0:22 ` Daniel Phillips
2008-01-09 8:04 ` Valdis.Kletnieks
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=47910D6E.3070801@garzik.org \
--to=jeff@garzik.org \
--cc=a1426z@gawab.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dgc@sgi.com \
--cc=hbryan@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=phillips@google.com \
--cc=ric@emc.com \
--cc=riel@redhat.com \
--cc=tytso@mit.edu \
--cc=val.henson@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.