From: Theodore Tso <tytso@mit.edu>
To: Gui Xiaohua <guixh@cn.fujitsu.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH: e2fsprogs: resize2fs failed when "mkfs.ext4 -O flex_bg"]
Date: Mon, 9 Feb 2009 20:09:17 -0500 [thread overview]
Message-ID: <20090210010917.GA30689@mini-me.lan> (raw)
In-Reply-To: <4990CB6A.1020403@cn.fujitsu.com>
On Tue, Feb 10, 2009 at 08:33:46AM +0800, Gui Xiaohua wrote:
> When mkfs.ext4 with flex_bg option, resize2fs with -M option will fail.
>
> Steps to reproduce:
>
> # mkfs.ext4 -O flex_bg /dev/sda6
> # resize2fs /dev/sda6 -M
>
> resize2fs: No space left on device while trying to resize /dev/sda6
These problems were fixed in e2fsprogs 1.41.4. See especially commit
id's 793a04a0 and 9227c5bb. (There were a number of other resize2fs
bugs fixed in 1.41.4, but these two relate to the problems you were
trying to solve.)
I'm not convinced your attempt at trying to guesstimate how the number
of extra blocks needed by counting fragments works for anything other
than an empty filesystem. If the filesystem is filled with contents,
and then it is shrunk, the resulting number of new extent blocks which
are needed is very much dependent on how the blocks end up getting
moved, and trying to determine the exact number up front is extremely
difficult.
Regards,
- Ted
next prev parent reply other threads:[~2009-02-10 1:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 0:33 [PATCH: e2fsprogs: resize2fs failed when "mkfs.ext4 -O flex_bg"] Gui Xiaohua
2009-02-10 1:09 ` Theodore Tso [this message]
2009-02-10 3:32 ` Gui Xiaohua
2009-02-10 16:48 ` Theodore Tso
2009-02-11 1:15 ` Gui Xiaohua
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=20090210010917.GA30689@mini-me.lan \
--to=tytso@mit.edu \
--cc=guixh@cn.fujitsu.com \
--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;
as well as URLs for NNTP newsgroup(s).