From: Theodore Ts'o <tytso@mit.edu>
To: Johan Harvyl <johan@harvyl.se>
Cc: Dave Chinner <david@fromorbit.com>,
Andreas Dilger <adilger@dilger.ca>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: resize2fs: Should never happen: resize inode corrupt! - lost key inodes
Date: Sat, 19 Sep 2015 11:02:25 -0400 [thread overview]
Message-ID: <20150919150225.GG2921@thunk.org> (raw)
In-Reply-To: <55FD6D26.1010706@harvyl.se>
On Sat, Sep 19, 2015 at 04:11:50PM +0200, Johan Harvyl wrote:
>
> Should this be reported in a bug tracker rather than here?
Yes, please do. I can reproduce this using e2fsprogs 1.43's next
branch, so there is definitely a real bug in e2fsprogs's resize2fs.
The fastest way to reproduce this is using tmpfs (it only requires
275MB of ram):
#!/bin/bash
FS=/tmp/foo.img
touch $FS
mkfs.ext4 $FS -i 262144 -m 0 -O 64bit 15627548672k
resize2fs -p $FS 19534435840k
resize2fs -p $FS 23441323008k
debugfs -c $FS -R "stat <2>"
Cheers,
- Ted
prev parent reply other threads:[~2015-09-19 15:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 18:15 resize2fs: Should never happen: resize inode corrupt! - lost key inodes Johan Harvyl
2015-08-11 22:47 ` Theodore Ts'o
2015-08-12 22:00 ` Johan Harvyl
2015-08-13 13:27 ` Theodore Ts'o
2015-08-13 18:12 ` Johan Harvyl
2015-09-03 22:16 ` Johan Harvyl
2015-09-12 10:27 ` Johan Harvyl
2015-09-14 21:35 ` Johan Harvyl
2015-09-15 17:55 ` Johan Harvyl
2015-09-17 1:21 ` Andreas Dilger
2015-09-18 18:26 ` Johan Harvyl
2015-09-19 2:47 ` Dave Chinner
2015-09-19 5:23 ` Darrick J. Wong
2015-09-19 14:11 ` Johan Harvyl
2015-09-19 15:02 ` 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=20150919150225.GG2921@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=david@fromorbit.com \
--cc=johan@harvyl.se \
--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.