From: Folkert van Heusden <folkert@vanheusden.com>
To: "Theodore Ts'o" <tytso@mit.edu>, John Stoffel <john@stoffel.org>,
Takashi Sato <sho@tnes.nec.co.jp>,
ext2-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Ext2-devel] Re: [PATCH] ext3: Extends blocksize up to pagesize
Date: Mon, 23 Jan 2006 21:36:02 +0100 [thread overview]
Message-ID: <20060123203602.GE10077@vanheusden.com> (raw)
In-Reply-To: <20060123054327.GN4124@schatzie.adilger.int>
> I think the work done by the U. Wisconsin group for IRON ext3 is the
> way to go (namely checksumming of filesystem metadata, and possibly
> some level of redundancy). This gives us concrete checks on what metadata
> is valid and the filesystem can avoid any (or further) corruption when
> the hardware goes bad. The existing ext3 code already has these checks,
> but as filesystems get larger the validity of a block number of an inode
> is harder to check because any value may be correct. Given that CPU
> speed is growing orders of magnitude faster than disk IO the overhead of
> checksumming is a reasonable thing to do these days (optionally, of course).
Then please make it optionally per mount-point.
E.g.: I don't care if the filesystem of the filestore of my Squid setup
goes bad (mke2fs will fix it just nicely) but I would get upset if its
OS filesystem would get corrupted.
Folkert van Heusden
--
Ever wonder what is out there? Any alien races? Then please support
the seti@home project: setiathome.ssl.berkeley.edu
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
next prev parent reply other threads:[~2006-01-23 20:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 13:06 [PATCH] ext3: Extends blocksize up to pagesize Takashi Sato
2006-01-18 15:48 ` John Stoffel
2006-01-22 18:28 ` Theodore Ts'o
2006-01-23 5:43 ` [Ext2-devel] " Andreas Dilger
2006-01-23 20:36 ` Folkert van Heusden [this message]
2006-01-23 8:30 ` Helge Hafting
2006-01-18 18:52 ` [Ext2-devel] " Andreas Dilger
2006-01-21 7:10 ` Andrew Morton
2006-01-22 18:31 ` Theodore Ts'o
2006-01-23 5:38 ` Andreas Dilger
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=20060123203602.GE10077@vanheusden.com \
--to=folkert@vanheusden.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=john@stoffel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sho@tnes.nec.co.jp \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).