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: Fri, 22 May 2015 08:37:26 -0400 [thread overview]
Message-ID: <555F2306.8010607@ubuntu.com> (raw)
In-Reply-To: <20150522022837.GC2750@thunk.org>
On 5/21/2015 10:28 PM, Theodore Ts'o wrote:
> On Thu, May 21, 2015 at 08:08:17PM -0400, Phillip Susi wrote:
> The change was that for uninitialized block bitmaps, dumpe2fs used to
> display incorrect information (that is, it would claim all of the
> blocks were free, even though in fact that was not true).
It seems to have actually been a change on disk, since e2defrag *used*
to count the number of free blocks assuming an uninitialized bitmap
meant that they were all free, and get the same number reported in the
superblock. This was probably prior to the change you are thinking of.
IIRC, when I looked using debugfs, the block groups containing metadata
always had their bitmaps initialized.
next prev parent reply other threads:[~2015-05-22 12:38 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
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 [this message]
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=555F2306.8010607@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).