From: "Jose R. Santos" <jrs@us.ibm.com>
To: Celine Bourde <celine.bourde@bull.net>
Cc: linux-ext4@vger.kernel.org, cmm@us.ibm.com,
"Frédéric Bohé" <frederic.bohe@bull.net>,
"SOLOFO RAMANGALAHY" <Solofo.Ramangalahy@bull.net>,
"Jean-Pierre Dion" <jean-pierre.dion@bull.net>
Subject: Re: [PATCH][e2fsprogs][mke2fs] fix FLEX_BG offset
Date: Thu, 3 Jul 2008 06:55:53 -0500 [thread overview]
Message-ID: <20080703065553.53c35979@gara> (raw)
In-Reply-To: <486C8BEE.5030200@bull.net>
On Thu, 03 Jul 2008 10:21:02 +0200
Celine Bourde <celine.bourde@bull.net> wrote:
> This patch resolves the offset problem of the flex_bg
> option when you use mke2fs tool.
>
> For example, if you type mkfs.ext4 -I256 -O flex_bg -G32 -E test_fs <device>
> and look dumpe2fs <device> result you will see an offset problem.
>
> Group 0: (Blocks 0-32767)
> Primary superblock at 0, Group descriptors at 1-5
> Reserved GDT blocks at 6-1024
> Block bitmap at 1025 (+1025), Inode bitmap at 1058 (+1058)
> Inode table at 1090-1601 (+1090)
> 0 free blocks, 8181 free inodes, 2 directories
> Free blocks:
> Free inodes: 12-8192
>
> Inode bitmap must start at 1025 + 32 = 1057
> In all flexbg groups, the block between the last block bitmap and the
> first inode
> bitmap (metatdata) is not used, which introduced a hole.
>
> This patch corrects it.
> You have to apply it on e2fsprogs (mke2fs 1.41-WIP (17-Jun-2008)) master
> branch.
>
> Celine Bourde.
Acked-by: Jose R. Santos <jrs@us.ibm.com>
-JRS
next prev parent reply other threads:[~2008-07-03 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 8:21 [PATCH][e2fsprogs][mke2fs] fix FLEX_BG offset Celine Bourde
2008-07-03 11:55 ` Jose R. Santos [this message]
2008-07-07 19:42 ` Jose R. Santos
2008-07-07 22:30 ` Theodore Tso
2008-07-07 16:46 ` Theodore Tso
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=20080703065553.53c35979@gara \
--to=jrs@us.ibm.com \
--cc=Solofo.Ramangalahy@bull.net \
--cc=celine.bourde@bull.net \
--cc=cmm@us.ibm.com \
--cc=frederic.bohe@bull.net \
--cc=jean-pierre.dion@bull.net \
--cc=linux-ext4@vger.kernel.org \
/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