LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Theodore Tso <tytso@mit.edu>, Al Boldi <a1426z@gawab.com>,
	Valerie Henson <val.henson@gmail.com>,
	Rik van Riel <riel@redhat.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [Patch] document ext3 requirements (was Re: [RFD] Incremental fsck)
Date: Tue, 15 Jan 2008 21:16:53 +0100	[thread overview]
Message-ID: <20080115201653.GA5639@elf.ucw.cz> (raw)
In-Reply-To: <20080113174125.5f39ac64@lxorguk.ukuu.org.uk>

Hi!

> > What are ext3 expectations of disk (is there doc somewhere)? For
> > example... if disk does not lie, but powerfail during write damages
> > the sector -- is ext3 still going to work properly?
> 
> Nope. However the few disks that did this rapidly got firmware updates
> because there are other OS's that can't cope.
> 
> > If disk does not lie, but powerfail during write may cause random
> > numbers to be returned on read -- can fsck handle that?
> 
> most of the time. and fsck knows about writing sectors to remove read
> errors in metadata blocks.
> 
> > What abou disk that kills 5 sectors around sector being written during
> > powerfail; can ext3 survive that?
> 
> generally. Note btw that for added fun there is nothing that guarantees
> the blocks around a block on the media are sequentially numbered. The
> usually are but you never know.

Ok, should something like this be added to the documentation?

It would be cool to be able to include few examples (modern SATA disks
support bariers so are safe, any IDE from 1989 is unsafe), but I do
not know enough about hw...

Signed-off-by: Pavel Machek <pavel@suse.cz>

diff --git a/Documentation/filesystems/ext3.txt b/Documentation/filesystems/ext3.txt
index b45f3c1..adfcc9d 100644
--- a/Documentation/filesystems/ext3.txt
+++ b/Documentation/filesystems/ext3.txt
@@ -183,6 +183,18 @@ mke2fs: 	create a ext3 partition with th
 debugfs: 	ext2 and ext3 file system debugger.
 ext2online:	online (mounted) ext2 and ext3 filesystem resizer
 
+Requirements
+============
+
+Ext3 needs disk that does not do write-back caching or disk that
+supports barriers and Linux configuration that can use them.
+
+* if disk damages the sector being written during powerfail, ext3
+  can't cope with that.  Fortunately, such disks got firmware updates
+  to fix this long time ago.
+
+* if disk writes random data during powerfail, ext3 should survive
+  that most of the time.
 
 References
 ==========


-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2008-01-15 20:17 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               ` Pavel Machek [this message]
2008-01-15 21:43                 ` [Patch] document ext3 requirements (was Re: [RFD] Incremental fsck) 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
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=20080115201653.GA5639@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=a1426z@gawab.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.com \
    --cc=tytso@mit.edu \
    --cc=val.henson@gmail.com \
    --subject='[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).