From: Valerie Clement <valerie.clement@bull.net>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: Problems with mballoc and uninit_groups option
Date: Fri, 11 Jan 2008 15:04:08 +0100 [thread overview]
Message-ID: <47877758.1070603@bull.net> (raw)
Hi,
I've got problems with mballoc when I create the ext4 filesystem with
the "uninit_groups" option enabled.
First, I do a single test on a filesystem created without the
"uninit_groups" option and mounted with the defaults option:
dd if=/dev/zero of=/mnt/test/foo bs=1M count=1024
In this case, the file blocks are allocated in the groups 4, 5, 6, 7, 8,
9, 10.
When the filesystem is created with the "uninit_groups" option enabled
and mounted with the defaults option, I do the same dd command.
In this case, the file blocks are allocated in the groups 5, 7, 9, 25,
27, 49, 81. It seems that the blocks could be allocated only in the
already initialized groups.
Who knows how to fix that?
Valérie
next reply other threads:[~2008-01-11 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 14:04 Valerie Clement [this message]
2008-01-11 15:45 ` Problems with mballoc and uninit_groups option Aneesh Kumar K.V
2008-01-14 14:05 ` Valerie Clement
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=47877758.1070603@bull.net \
--to=valerie.clement@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