From: "Jose R. Santos" <jrs@us.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Andreas Dilger <adilger@clusterfs.com>,
linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: Initial results of FLEX_BG feature.
Date: Thu, 12 Jul 2007 10:09:06 -0500 [thread overview]
Message-ID: <20070712100906.2e2afb9c@gara> (raw)
In-Reply-To: <20070711221425.GH19456@thunk.org>
On Wed, 11 Jul 2007 18:14:25 -0400
Theodore Tso <tytso@mit.edu> wrote:
> On Wed, Jul 11, 2007 at 12:30:04AM -0500, Jose R. Santos wrote:
> > Right now what I've done is allocate the bitmaps and inode tables at the
> > beginning of each group of 64 BG. Still need to work on fsck since just
> > removing the restriction on were the bitmaps and inode table are
> > located still gives me errors of uninitialized inodes with dtime set.
> > Seems like fsck still expect inode information to be located at
> > specific locations within the disk.
>
> Can you send me the patch which you were playing with? I might be
> able to help you with this. It should be pretty straightforward to
> remove the constraint on the inode table location.
Here is the kernel piece.
-JRS
---
fs/ext4/super.c | 3 3 + 0 - 0 !
include/linux/ext4_fs.h | 4 3 + 1 - 0 !
2 files changed, 6 insertions(+), 1 deletion(-)
Index: linux-2.6/fs/ext4/super.c
===================================================================
--- linux-2.6.orig/fs/ext4/super.c 2007-07-11 15:34:58.000000000 -0500
+++ linux-2.6/fs/ext4/super.c 2007-07-11 16:19:08.000000000 -0500
@@ -1271,6 +1271,9 @@ static int ext4_check_descriptors (struc
ext4_debug ("Checking group descriptors");
+ if (EXT4_HAS_INCOMPAT_FEATURE(sb, EXT4_FEATURE_INCOMPAT_FLEX_BG))
+ return 1;
+
for (i = 0; i < sbi->s_groups_count; i++)
{
if (i == sbi->s_groups_count - 1)
Index: linux-2.6/include/linux/ext4_fs.h
===================================================================
--- linux-2.6.orig/include/linux/ext4_fs.h 2007-07-11 15:34:58.000000000 -0500
+++ linux-2.6/include/linux/ext4_fs.h 2007-07-12 09:58:51.000000000 -0500
@@ -698,13 +698,15 @@ static inline int ext4_valid_inum(struct
#define EXT4_FEATURE_INCOMPAT_META_BG 0x0010
#define EXT4_FEATURE_INCOMPAT_EXTENTS 0x0040 /* extents support */
#define EXT4_FEATURE_INCOMPAT_64BIT 0x0080
+#define EXT4_FEATURE_INCOMPAT_FLEX_BG 0x0200
#define EXT4_FEATURE_COMPAT_SUPP EXT2_FEATURE_COMPAT_EXT_ATTR
#define EXT4_FEATURE_INCOMPAT_SUPP (EXT4_FEATURE_INCOMPAT_FILETYPE| \
EXT4_FEATURE_INCOMPAT_RECOVER| \
EXT4_FEATURE_INCOMPAT_META_BG| \
EXT4_FEATURE_INCOMPAT_EXTENTS| \
- EXT4_FEATURE_INCOMPAT_64BIT)
+ EXT4_FEATURE_INCOMPAT_64BIT| \
+ EXT4_FEATURE_INCOMPAT_FLEX_BG)
#define EXT4_FEATURE_RO_COMPAT_SUPP (EXT4_FEATURE_RO_COMPAT_SPARSE_SUPER| \
EXT4_FEATURE_RO_COMPAT_LARGE_FILE| \
EXT4_FEATURE_RO_COMPAT_DIR_NLINK | \
next prev parent reply other threads:[~2007-07-12 15:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 16:23 Initial results of FLEX_BG feature Jose R. Santos
2007-07-11 4:12 ` Andreas Dilger
2007-07-11 5:30 ` Jose R. Santos
2007-07-11 5:39 ` Eric Sandeen
2007-07-11 12:41 ` Andreas Dilger
2007-07-11 22:09 ` Theodore Tso
2007-07-11 22:14 ` Theodore Tso
2007-07-12 15:02 ` Jose R. Santos
2007-07-12 15:09 ` Jose R. Santos [this message]
2007-07-16 6:34 ` Andreas Dilger
2007-07-16 12:27 ` Jose R. Santos
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=20070712100906.2e2afb9c@gara \
--to=jrs@us.ibm.com \
--cc=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--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).