From: Phillip Susi <psusi@ubuntu.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: resize2fs minimum size wrong
Date: Sat, 23 May 2015 17:18:41 -0400 [thread overview]
Message-ID: <5560EEB1.8070003@ubuntu.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
So I have a filesystem with nothing beyond group 16 used ( including
metadata ), so it should be able to shrink to ~524288 blocks, yet
resize2fs claims the minimum size is 770083 blocks. Resize debug output
follows:
resize2fs 1.43-WIP (29-Mar-2015)
fs has 52108 inodes, 7 groups required.
fs requires 492169 data blocks.
With 7 group(s), we have 218842 blocks available.
Added 9 extra group(s), blks_needed 492169, data_blocks 513754,
last_start 224238
Last group's overhead is 10534
Need 267931 data blocks in last group
Final size of last group is 278465
Estimated blocks needed: 769985
Extents safety margin: 98
Estimated minimum size of the filesystem: 770083
So clearly it thinks only 16 block groups are enough, then somehow leaps
from there to 24.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCgAGBQJVYO6xAAoJENRVrw2cjl5RDSUH/1bCpLZ/oxj/zoeFnLgjHDvI
UMiR4sJhtEC2pYxBFatz9DOg3iDsEQvN+tJ3lcVb4l8rn6pFepGaNljxiMk8uWae
U784u/jd5UNbYSftKtC/Y9MkH9bfcWKR9wAmWvGz9gSjJXb5SeqGo4yQZTFkhPK8
vW3jvJ7YCCWqLh/VGGunq6jJaGPGVsstlMOEKvQjdEdd0zhXp3YyMy2+GfBlsvkd
PO1780FjG07s+VS4DRwktNNrWIB8TFxM0TsslDrd8ImB6xSssbbPbVI5T81MrhR1
QwO4q/ql4XAwy57rzmxmzf75HhpjUN69ySBm6VA5N2eyiJqOqY3sBz6wZ01LG/I=
=dht/
-----END PGP SIGNATURE-----
next reply other threads:[~2015-05-23 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 21:18 Phillip Susi [this message]
2015-05-23 23:36 ` resize2fs minimum size wrong Theodore Ts'o
2015-05-24 0:27 ` Phillip Susi
2015-05-24 1:34 ` Theodore Ts'o
2015-05-24 3:02 ` [PATCH] resize2fs: fix minimum size calculation Phillip Susi
2015-06-18 0:55 ` 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=5560EEB1.8070003@ubuntu.com \
--to=psusi@ubuntu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.