From: Andreas Dilger <adilger@clusterfs.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: 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 14:25:03 -0700 [thread overview]
Message-ID: <20051031212503.GY31368@schatzie.adilger.int> (raw)
In-Reply-To: <20051031001334.GP4180@stusta.de>
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.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2005-10-31 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 0:13 Adrian Bunk
2005-10-31 21:25 ` Andreas Dilger [this message]
2005-11-01 4:46 ` Theodore Ts'o
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=20051031212503.GY31368@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®