From: Jianchao Wang <jianchao.wan9@gmail.com>
To: Artem Blagodarenko <artem.blagodarenko@gmail.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu, adilger.kernel@dilger.ca
Subject: Re: [HELP] What are the allocated blocks on a newly created ext4 fs ?
Date: Mon, 10 Jun 2019 11:25:47 +0800 [thread overview]
Message-ID: <22ccd72a-8926-0d12-0fbe-8ad5604d1584@gmail.com> (raw)
In-Reply-To: <7FD3148B-1E27-4BFA-965C-9FDC7FC8FD96@gmail.com>
Hi Artem
Thanks so much for your help.
On 2019/6/6 20:32, Artem Blagodarenko wrote:
> Hello Jianchao,
>
> Not enought input data to give an answer. It depends on mkfs options. For example, if flex_bg option is enabled, then several block groups are tied together as one logical block group; the bitmap spaces and the inode table space in the first block group, so some groups are not totally free just after FS creating.
In my environment, there are 16 bgs per flex_bg.
The bitmaps and inode table .etc should lay on the first bg of every flex_bg.
So I can see there are about 8223 blocks allocated in the 1st bg of every flex_bg.
But as you can see in the output of mb_groups, there are some bgs which get allocated about 1024 blocks.
I have out figured out what are they for.
Thanks
Jianchao
>
>> On 6 Jun 2019, at 13:41, Jianchao Wang <jianchao.wan9@gmail.com> wrote:
>>
>> Dear all
>>
>> After I newly created a ext4 fs and check the mb_group,
>>
>> #group: free frags first [ 2^0 2^1 2^2 2^3 2^4 2^5 2^6 2^7 2^8 2^9 2^10 2^11 2^12 2^13 ]
>> #0 : 23513 1 9255 [ 1 0 0 1 1 0 1 1 1 1 0 1 1 2 ]
>> #1 : 31743 1 1025 [ 1 1 1 1 1 1 1 1 1 1 0 1 1 3 ]
>> ^^^^
>> #2 : 32768 1 0 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 4 ]
>> #3 : 31743 1 1025 [ 1 1 1 1 1 1 1 1 1 1 0 1 1 3 ]
>> #4 : 32768 1 0 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 4 ]
>> #5 : 31743 1 1025 [ 1 1 1 1 1 1 1 1 1 1 0 1 1 3 ]
>> #6 : 32768 1 0 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 4 ]
>> #7 : 31743 1 1025 [ 1 1 1 1 1 1 1 1 1 1 0 1 1 3 ]
>> #8 : 32768 1 0 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 4 ]
>> #9 : 31743 1 1025 [ 1 1 1 1 1 1 1 1 1 1 0 1 1 3 ]
>> #10 : 32768 1 0 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 4 ]
>> #11 : 32768 1 0 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 4 ]
>>
>> There are some bgs that have 1024 blocks allocated. What are they for ?
>>
> BTW, I don’t see from mb_group output why 1024 blocks allocated in group #1
>> Many thanks in advance
>> Jianchao
>
> Best regards,
> Artem Blagodarenko.
>
next prev parent reply other threads:[~2019-06-10 3:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 10:41 [HELP] What are the allocated blocks on a newly created ext4 fs ? Jianchao Wang
2019-06-06 12:32 ` Artem Blagodarenko
2019-06-10 3:25 ` Jianchao Wang [this message]
2019-06-10 3:39 ` Theodore Ts'o
2019-06-10 3:54 ` Jianchao Wang
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=22ccd72a-8926-0d12-0fbe-8ad5604d1584@gmail.com \
--to=jianchao.wan9@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=artem.blagodarenko@gmail.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).