From: Theodore Ts'o <tytso@mit.edu>
To: Phillip Susi <psusi@ubuntu.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: Unused block group, but all blocks not free?
Date: Thu, 21 May 2015 22:28:38 -0400 [thread overview]
Message-ID: <20150522022837.GC2750@thunk.org> (raw)
In-Reply-To: <555E7371.9060207@ubuntu.com>
On Thu, May 21, 2015 at 08:08:17PM -0400, Phillip Susi wrote:
>
> I wonder though, why I didn't see these problems the last time I used
> e2defrag, which was probably 2 years ago and was on a filesystem with
> a resize inode, and flex_bg and uninitialized bitmaps. At the time it
> seemed that uninitialized bitmaps were not used on groups with blocks
> used for these sorts of things. I guess that must also be a more
> recent change.
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).
People complained this wasn't actually accurate, so what we are
currently doing is considered more correct(tm).
- Ted
next prev parent reply other threads:[~2015-05-22 2:28 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 [this message]
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=20150522022837.GC2750@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=psusi@ubuntu.com \
/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).