From: "Theodore Ts'o" <tytso@mit.edu>
To: Adrian Bunk <bunk@stusta.de>,
ext2-devel@lists.sourceforge.net, sct@redhat.com, akpm@osdl.org,
ext3-users@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: What is the history of CONFIG_EXT{2,3}_CHECK?
Date: Mon, 31 Oct 2005 23:46:58 -0500 [thread overview]
Message-ID: <20051101044658.GA7500@thunk.org> (raw)
In-Reply-To: <20051031212503.GY31368@schatzie.adilger.int>
On Mon, Oct 31, 2005 at 02:25:03PM -0700, Andreas Dilger wrote:
> On Oct 31, 2005 01:13 +0100, Adrian Bunk wrote:
> > Can anyone tell me the history of CONFIG_EXT{2,3}_CHECK?
> >
> > There is code for a "check" option for mount if these options are
> > enabled, but there's no way to enable them.
>
> These are expensive debugging options, which walk the inode/block bitmaps
> for getting the group inode/block usage instead of using the group
> summary data. Not used very often but I suspect occasionally useful for
> developers mucking with ext[23] internals. Since it is developer-only
> code it needs to be enabled with #define CONFIG_EXT[23]_CHECK in a
> header or compile option.
It's basically a stripped down version of e2fsck pass #5, though. Is
there any reason why this needs to be in the kernel? If it would be
useful I could easily make a userspace implementation of these checks.
- Ted
next prev parent reply other threads:[~2005-11-01 4:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 0:13 What is the history of CONFIG_EXT{2,3}_CHECK? Adrian Bunk
2005-10-31 21:25 ` Andreas Dilger
2005-11-01 4:46 ` Theodore Ts'o [this message]
2005-11-07 21:18 ` [2.6 patch] remove CONFIG_EXT{2,3}_CHECK Adrian Bunk
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=20051101044658.GA7500@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=ext2-devel@lists.sourceforge.net \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.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.