From: Theodore Ts'o <tytso@mit.edu>
To: Mark Casey <markc@unifiedgroup.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Question on resize2fs with "combination of flex_bg and !resize_inode"
Date: Thu, 8 Nov 2012 18:03:08 -0500 [thread overview]
Message-ID: <20121108230308.GN19977@thunk.org> (raw)
In-Reply-To: <k7h36p$qgp$1@ger.gmane.org>
On Thu, Nov 08, 2012 at 02:03:38PM -0600, Mark Casey wrote:
> Regarding this patch to resize2fs:
> http://permalink.gmane.org/gmane.comp.file-systems.ext4/7379
>
> In reading the comment, I was wondering if this problem scenario can
> also happen when shrinking an ext4 filesystem with this combination
> of features, or if it is only likely to be a problem when growing
> it?
It's only a problem when growing the file system. The comment in the
patch explains the situation; when you are shrinking the file system,
there is never any need to move inode tables to make room for the new
block group descriptor blocks --- which are necessitated by the
additional block groups that come from growing the file system.
- Ted
prev parent reply other threads:[~2012-11-08 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 20:03 Question on resize2fs with "combination of flex_bg and !resize_inode" Mark Casey
2012-11-08 23:03 ` Theodore Ts'o [this message]
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=20121108230308.GN19977@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=markc@unifiedgroup.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).