| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sat, 19 Sep 2015 12:47:25 +1000 From: Dave Chinner <david@...morbit.com> To: Andreas Dilger <adilger@...ger.ca> Cc: Johan Harvyl <johan@...vyl.se>, Theodore Ts'o <tytso@....edu>, "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org> Subject: Re: resize2fs: Should never happen: resize inode corrupt! - lost key inodes On Wed, Sep 16, 2015 at 07:21:59PM -0600, Andreas Dilger wrote: > If you add "-b 1024" to the mke2fs command line to use 1KB instead of 4KB blocks, and reduce the sizes by a factor of 4 does the problem still happen? That would make it easier for someone else to test, since it would only need a 4-5TB disk instead of a 19Tb array. Sparse files on XFS using loopback will allow you to simulate devices larger than 16TB easily. You can turtle it all the way down, too, to create the xfs filesystem on a loopback device on a sparse file on ext4.... Doing this sort of thing lets me know, for example, that the mkfs.ext4 defaults fail on a 500TB device... # xfs_io -f -c 'truncate 500t' /mnt/xfs/fs.img # ls -lh /mnt/xfs total 0 -rw------- 1 root root 500T Sep 19 12:41 fs.img # mkfs.ext4 /mnt/xfs/fs.img mke2fs 1.42.13 (17-May-2015) /mnt/xfs/fs.img: Cannot create filesystem with requested number of inodes while setting up superblock # Cheers, Dave. -- Dave Chinner david@...morbit.com -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists