From: "Theodore Ts'o" <tytso@mit.edu>
To: Valerie Henson <val_henson@linux.intel.com>
Cc: Andrew Morton <akpm@osdl.org>,
pbadari@gmail.com, linux-kernel@vger.kernel.org,
Ext2-devel@lists.sourceforge.net, arjan@linux.intel.com,
zach.brown@oracle.com
Subject: Re: [Ext2-devel] [RFC] [PATCH] Reducing average ext2 fsck time through fs-wide dirty bit]
Date: Fri, 24 Mar 2006 13:52:38 -0500 [thread overview]
Message-ID: <20060324185237.GB18020@thunk.org> (raw)
In-Reply-To: <20060324143239.GB14508@goober>
On Fri, Mar 24, 2006 at 06:32:39AM -0800, Valerie Henson wrote:
> Note that ext3's habit of clearing indirect blocks on truncate would
> break some things I want to do in the future. (Insert secret plans
> here.)
This is fixable, but it would require making the truncate code (even
more) complicated.....
- Ted
next prev parent reply other threads:[~2006-03-24 18:52 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
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 [this message]
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=20060324185237.GB18020@thunk.org \
--to=tytso@mit.edu \
--cc=Ext2-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@gmail.com \
--cc=val_henson@linux.intel.com \
--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.