From: Phil Susi <psusi@ubuntu.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: Unused block group, but all blocks not free?
Date: Wed, 20 May 2015 11:15:59 -0400 [thread overview]
Message-ID: <555CA52F.3010109@ubuntu.com> (raw)
In-Reply-To: <20150520151007.GK2871@thunk.org>
On 5/20/2015 11:10 AM, Theodore Ts'o wrote:
> Have you checked to see if the metadata for other block groups are
> taking up space in the block group. This can happen when using the
> flex_bg layout. (And without flex_bg, then *all* block groups will
> always have blocks in use, for their own metadata blocks.)
That was my first thought and no, they aren't. The metadata is in bg 0
and bg 32, not 25. Even still, when the metadata is there, shouldn't
the allocation bitmap mark those blocks as in use rather than be
uninitialized?
next prev parent reply other threads:[~2015-05-20 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 1:10 Unused block group, but all blocks not free? Phillip Susi
2015-05-20 15:10 ` Theodore Ts'o
2015-05-20 15:15 ` Phil Susi [this message]
2015-05-20 16:31 ` Theodore Ts'o
[not found] ` <555D0541.1000804@ubuntu.com>
2015-05-21 23:59 ` Theodore Ts'o
2015-05-22 0:08 ` Phillip Susi
2015-05-22 2:28 ` Theodore Ts'o
2015-05-22 12:37 ` Phil Susi
2015-05-23 3:05 ` Theodore Ts'o
2015-05-23 15:39 ` Phillip Susi
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=555CA52F.3010109@ubuntu.com \
--to=psusi@ubuntu.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).