LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ric Wheeler <ric@emc.com>
To: Theodore Tso <tytso@mit.edu>,
	Daniel Phillips <phillips@google.com>,
	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>,
	Rik van Riel <riel@redhat.com>,
	Valerie Henson <val.henson@gmail.com>
Subject: Re: [Patch] document ext3 requirements (was Re: [RFD] Incremental fsck)
Date: Thu, 17 Jan 2008 18:18:05 -0500	[thread overview]
Message-ID: <478FE22D.9030907@emc.com> (raw)
In-Reply-To: <20080117224530.GH5547@mit.edu>

Theodore Tso wrote:
> On Wed, Jan 16, 2008 at 09:02:50PM -0500, Daniel Phillips wrote:
>> Have you observed that in the wild?  A former engineer of a disk drive
>> company suggests to me that the capacitors on the board provide enough
>> power to complete the last sector, even to park the head.
>>

Even if true (which I doubt), this is not implemented.

A modern drive can have 16-32 MB of write cache. Worst case, those 
sectors are not sequential which implies lots of head movement.

> 
> The problem isn't with the disk drive; it's from the DRAM, which tend
> to be much more voltage sensitive than the hard drives --- so it's
> quite likely that you could end up DMA'ing garbage from the memory.
> In fact the fact that the disk drives lasts longer due to capacitors
> on the board, rotational inertia of the platters, etc., is part of the
> problem.

I can tell you directly that when you drop power to a drive, you will 
lose write cache data if the write cache is enabled. With barriers 
enabled, our testing shows that file systems survive power failures 
which routinely caused corruption without them ;-)

ric



  parent reply	other threads:[~2008-01-17 23:21 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 [this message]
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
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=478FE22D.9030907@emc.com \
    --to=ric@emc.com \
    --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=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).