LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bryan Henderson <hbryan@us.ibm.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: 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>, Ric Wheeler <ric@emc.com>,
Rik van Riel <riel@redhat.com>, Theodore Tso <tytso@mit.edu>,
Valerie Henson <val.henson@gmail.com>
Subject: Re: [Patch] document ext3 requirements (was Re: [RFD] Incremental fsck)
Date: Fri, 18 Jan 2008 09:43:25 -0800 [thread overview]
Message-ID: <OFC2B46E42.BDE3F6A4-ON882573D4.0060B268-882573D4.00615C9C@us.ibm.com> (raw)
In-Reply-To: <4790C0EE.10207@zytor.com>
"H. Peter Anvin" <hpa@zytor.com> wrote on 01/18/2008 07:08:30 AM:
> Bryan Henderson wrote:
> >
> > We weren't actually talking about writing out the cache. While that
was
> > part of an earlier thread which ultimately conceded that disk drives
most
> > probably do not use the spinning disk energy to write out the cache,
the
> > claim was then made that the drive at least survives long enough to
finish
> > writing the sector it was writing, thereby maintaining the integrity
of
> > the data at the drive level. People often say that a disk drive
> > guarantees atomic writes at the sector level even in the face of a
power
> > failure.
> >
> > 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.
> >
>
> A disk drive whose power is cut needs to have enough residual power to
> park its heads (or *massive* data loss will occur), and at that point it
> might as well keep enough on hand to finish an in-progress sector write.
>
> There are two possible sources of onboard temporary power: a large
> enough capacitor, or the rotational energy of the platters (an
> electrical motor also being a generator.) I don't care which one they
> use, but they need to do something.
I believe the power for that comes from a third source: a spring. Parking
the heads is too important to leave to active circuits.
--
Bryan Henderson IBM Almaden Research Center
San Jose CA Filesystems
next prev parent reply other threads:[~2008-01-18 17:44 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
2008-01-18 22:35 ` Bryan Henderson
2008-01-18 15:08 ` H. Peter Anvin
2008-01-18 17:43 ` Bryan Henderson [this message]
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=OFC2B46E42.BDE3F6A4-ON882573D4.0060B268-882573D4.00615C9C@us.ibm.com \
--to=hbryan@us.ibm.com \
--cc=a1426z@gawab.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dgc@sgi.com \
--cc=hpa@zytor.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 \
--subject='Re: [Patch] document ext3 requirements (was Re: [RFD] Incremental fsck)' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).