From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: Another resize issue - corruption case
Date: Thu, 21 Feb 2013 10:25:20 -0600 [thread overview]
Message-ID: <51264A70.3010106@redhat.com> (raw)
Again, for posterity, and in case anyone starts to dig into resize soon:
Bug 913245 - resize2fs w/ large block & inode count is going badly
https://bugzilla.redhat.com/show_bug.cgi?id=913245
Contains a fair bit of weirdness, but the outright problematic bug is that it's allowing the number of inodes to grow past 2^32. Loopback reproducer is in the bug.
The fs ends up quite corrupt, as well, and seems to not be growing by the correct amount, etc.
Seems like resize needs a lot of love still.
-Eric
reply other threads:[~2013-02-21 16:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51264A70.3010106@redhat.com \
--to=sandeen@redhat.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.