Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Agreed; thanks for finding this.
I also need to take Lukas' patch which enables 64bit by default.
We should re-check with both of those patches in place to make sure everything works properly...
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Description of problem: resize2fs cannot do online enlarge if 64bit feature is enabled explicitly at mkfs time. [root@ibm-x3690x5-01 resize]# uname -a Linux ibm-x3690x5-01.rhts.eng.nay.redhat.com 3.10.0-0.rc7.64.el7.x86_64 #1 SMP Tue Jun 25 10:00:04 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux [root@ibm-x3690x5-01 resize]# rpm -q e2fsprogs e2fsprogs-1.42.7-2.el7.x86_64 [root@ibm-x3690x5-01 resize]# truncate -s 50t fs.img [root@ibm-x3690x5-01 resize]# mkfs -t ext4 -O 64bit -F fs.img 17t mke2fs 1.42.7 (21-Jan-2013) Discarding device blocks: done Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 285212672 inodes, 4563402752 blocks 228170137 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=6710886400 139264 block groups 32768 blocks per group, 32768 fragments per group 2048 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000, 214990848, 512000000, 550731776, 644972544, 1934917632, 2560000000, 3855122432 Allocating group tables: done Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done [root@ibm-x3690x5-01 resize]# losetup -f /dev/loop0 [root@ibm-x3690x5-01 resize]# losetup /dev/loop0 fs.img [root@ibm-x3690x5-01 resize]# mount /dev/loop0 /mnt/ext4 [root@ibm-x3690x5-01 resize]# resize2fs /dev/loop0 resize2fs 1.42.7 (21-Jan-2013) Filesystem at /dev/loop0 is mounted on /mnt/ext4; on-line resizing required old_desc_blocks = 2176, new_desc_blocks = 6400 resize2fs: Invalid argument While checking for on-line resizing support And dmesg shows: [270491.166051] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null) [270491.173946] SELinux: initialized (dev loop0, type ext4), uses xattr [270500.004850] EXT4-fs (loop0): resizing filesystem from 4563402752 to 13421772800 blocks [270510.011347] EXT4-fs (loop0): resized to 4710727680 blocks [270520.045883] EXT4-fs (loop0): resized to 4852809728 blocks [270530.058412] EXT4-fs (loop0): resized to 4991746048 blocks [270540.097639] EXT4-fs (loop0): resized to 5123866624 blocks [270550.131691] EXT4-fs (loop0): resized to 5256511488 blocks [270560.133524] EXT4-fs (loop0): resized to 5383389184 blocks [270570.137817] EXT4-fs (loop0): resized to 5509218304 blocks [270580.151840] EXT4-fs (loop0): resized to 5629804544 blocks [270590.167257] EXT4-fs (loop0): resized to 5748293632 blocks [270594.974925] EXT4-fs warning (device loop0): verify_reserved_gdb:700: reserved GDT 2769 missing grp 177147 (5804755665) [270594.985813] EXT4-fs (loop0): resized filesystem to 6710886400 [270595.738493] EXT4-fs warning (device loop0): ext4_group_extend:1710: can't shrink FS - resize aborted Version-Release number of selected component (if applicable): e2fsprogs-1.42.7-2.el7 How reproducible: always Steps to Reproduce: 1. truncate -s 50t fs.img 2. losetup /dev/loop0 fs.img 3. mkfs -t ext4 -O 64bit /dev/loop0 4. mount /dev/loop0 /mnt/ext4 5. resize2fs /dev/loop0 Actual results: resize2fs reports "resize2fs: Invalid argument While checking for on-line resizing support" Expected results: resize2fs could enlarge fs Additional info: I proposed a patch for mke2fs upstream to disable resize_inode feature when creating >16T ext4 with 64bit feature enabled http://www.spinics.net/lists/linux-ext4/msg38920.html