linux-ext4 - Re: resize2fs running out of reserved gdb blocks.

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]

Message-ID: <20121112144020.GD4895@thunk.org>
Date:	Mon, 12 Nov 2012 09:40:20 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Kimmo Mustonen <k-20121112-81452+linux-ext4@...mmola.net>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: resize2fs running out of reserved gdb blocks.

On Mon, Nov 12, 2012 at 01:21:32PM +0200, Kimmo Mustonen wrote:
> I have an ext4 partition that seems to have used all reserved gdt blocks.

The original on-line resize scheme required gdt blocks to be reserved
so there would be room for the group descriptor table blocks (which
had to be contiguous).  The number of group descriptor blocks that was
reserved calculated to be a thousand times the size of the original
file system, which would normally be enough.  *But* it was also capped
by a limitation in how we reserved the gdt blocks such that the sum of
the in-use gdt blocks plus reserved gdt blocks could not exceed 1024
blocks.  Before the 64-bit option, this was not a problem, since we
would hit the 16T limitation at the same time.  However, when the
64-bit option is enabled, it's possible to run out of gdt blocks using
the old scheme; this is the limitation which you hit.

In the very latest kernels, we have added a new on-line resizing
scheme, which does not require that block group descriptors be
contiguous.  However, it requires the very latest version of e2fsprogs
(1.42.6) and the to-be-released 3.7 kernel (the new on-line resizing
code landed in 3.7-rc1, during the merge window).

If you are willing to temporarily boot a bleeding edge 3.7 kernel and
use the resize2fs from e2fsprogs 1.42.6, you'll be able to resizing
your partition.  After you do this, you could fall back to the Debian
stable kernel and things should work w/o problems; the latest kernel
and e2fsprogs code is needed just for the online resize operation.
The resulting file system will be recognized by older kernels and
e2fsprogs programs.

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