linux-ext4 - Re: [PATCH: e2fsprogs: resize2fs failed when "mkfs.ext4 -O flex

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 9 Feb 2009 20:09:17 -0500
From:	Theodore Tso <tytso@....edu>
To:	Gui Xiaohua <guixh@...fujitsu.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [PATCH: e2fsprogs: resize2fs failed when "mkfs.ext4 -O
	flex_bg"]

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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html