From: Valerie Henson <val_henson@linux.intel.com>
To: Badari Pulavarty <pbadari@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
ext2-devel <Ext2-devel@lists.sourceforge.net>,
Arjan van de Ven <arjan@linux.intel.com>,
"Theodore Ts'o" <tytso@mit.edu>,
Zach Brown <zach.brown@oracle.com>
Subject: Re: [Ext2-devel] [RFC] [PATCH] Reducing average ext2 fsck time through fs-wide dirty bit]
Date: Wed, 22 Mar 2006 14:48:45 -0800 [thread overview]
Message-ID: <20060322224844.GU12571@goober> (raw)
In-Reply-To: <1143054558.6086.61.camel@dyn9047017100.beaverton.ibm.com>
On Wed, Mar 22, 2006 at 11:09:18AM -0800, Badari Pulavarty wrote:
> On Tue, 2006-03-21 at 17:10 -0800, Valerie Henson wrote:
> > Hi all,
> >
> > I am working on reducing the average time spent on fscking ext2 file
> > systems. My initial take on the problem is to avoid fscking when the
>
> Just curious, why are you teaching ext2 same tricks that are in ext3 ?
> Is there a reason behind improving ext2 ? Are there any benefits
> of not using ext3 instead ?
ext2 is simpler and faster than ext3 in many cases. This is sort of
cheating; ext2 is simpler and faster because it makes no effort to
maintain on-disk consistency and can skip annoying things like, oh,
reserving space in the journal. I am looking for ways to make ext2
cheat even more.
-VAL
next prev parent reply other threads:[~2006-03-22 22:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 1:10 [RFC] [PATCH] Reducing average ext2 fsck time through fs-wide dirty bit] Valerie Henson
2006-03-22 8:40 ` Valerie Henson
2006-03-22 13:08 ` Alan Cox
2006-03-22 18:18 ` [Ext2-devel] " Mingming Cao
2006-03-22 18:16 ` [Ext2-devel] " Mingming Cao
[not found] ` <200603230011.53793.ioe-lkml@rameria.de>
2006-03-22 23:52 ` Mingming Cao
2006-03-22 19:09 ` Badari Pulavarty
2006-03-22 22:48 ` Valerie Henson [this message]
2006-03-23 1:55 ` Andrew Morton
2006-03-24 14:32 ` Valerie Henson
2006-03-24 15:35 ` Dave Kleikamp
2006-03-24 18:48 ` Andrew Morton
2006-03-24 19:13 ` Mingming Cao
2006-03-24 19:31 ` Andreas Dilger
2006-03-24 18:52 ` Theodore Ts'o
2006-03-24 19:14 ` Mingming Cao
2006-03-24 19:28 ` Andreas Dilger
2006-03-24 20:01 ` Theodore Ts'o
2006-03-24 21:00 ` Andreas Dilger
2006-03-24 21:39 ` Theodore Ts'o
2006-03-24 22:16 ` Andreas Dilger
2006-03-25 5:13 ` Suparna Bhattacharya
2006-03-25 17:38 ` Ben Pfaff
2006-03-24 20:52 ` [Ext2-devel] " Matthew Wilcox
2006-03-24 21:23 ` 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=20060322224844.GU12571@goober \
--to=val_henson@linux.intel.com \
--cc=Ext2-devel@lists.sourceforge.net \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@gmail.com \
--cc=tytso@mit.edu \
--cc=zach.brown@oracle.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.