Re: resize2fs: Should never happen: resize inode corrupt! - lost key inodes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux