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.
Description of problem:
dumpe2fs fails to read ext4 image created with "meta_bg, ^resize_inode" with
"
dumpe2fs: Bad magic number in super-block while trying to open 512M.e2img
Couldn't find valid filesystem superblock.
"
On x86_64, dumpe2fs of the same version can well read the same image.
It's not a regression on RHEL-7.8, the same problem can reproduced with e2fsprogs-1.42.9-4.el7 (RHEL-7.0 GA).
Please check "Steps to Reproduce" below for reproduction.
ppc64 with e2fsprogs-1.42.9-17.el7
"""
[root@ibm-p8-kvm-09-guest-12 ~]# rpm -q e2fsprogs && fallocate -l 512M 512M.img && mkfs.ext4 -qF -O meta_bg,^resize_inode 512M.img && e2image 512M.img 512M.e2img && dumpe2fs -i 512M.e2img
e2fsprogs-1.42.9-17.el7.ppc64
e2image 1.42.9 (28-Dec-2013)
dumpe2fs 1.42.9 (28-Dec-2013)
dumpe2fs: Bad magic number in super-block while trying to open 512M.e2img
Couldn't find valid filesystem superblock.
"""
x86_64 with e2fsprogs-1.42.9-17.el7
"""
[root@virt-12 ~]# rpm -q e2fsprogs && fallocate -l 512M 512M.img && mkfs.ext4 -qF -O meta_bg,^resize_inode 512M.img && e2image 512M.img 512M.e2img && dumpe2fs -i 512M.e2img
e2fsprogs-1.42.9-17.el7.x86_64
e2image 1.42.9 (28-Dec-2013)
dumpe2fs 1.42.9 (28-Dec-2013)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 9d82c821-9d43-4ab5-a600-05ac1d22ee85
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr dir_index filetype meta_bg extent 64bit flex_bg sparse_super huge_file uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 32768
Block count: 131072
Reserved block count: 6553
Free blocks: 124910
Free inodes: 32757
First block: 0
Block size: 4096
Fragment size: 4096
Group descriptor size: 64
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Flex block group size: 16
Filesystem created: Mon Feb 24 08:46:16 2020
Last mount time: n/a
Last write time: Mon Feb 24 08:46:16 2020
Mount count: 0
Maximum mount count: -1
Last checked: Mon Feb 24 08:46:16 2020
Check interval: 0 (<none>)
Lifetime writes: 16 MB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 7e1b00a7-9248-46be-b6e7-83b411b12c49
Journal backup: inode blocks
...
"""
Version-Release number of selected component (if applicable):
e2fsprogs-1.42.9-17.el7
How reproducible:
Always
Steps to Reproduce:
1. rpm -q e2fsprogs && fallocate -l 512M 512M.img && mkfs.ext4 -qF -O meta_bg,^resize_inode 512M.img && e2image 512M.img 512M.e2img && dumpe2fs -i 512M.e2img
Actual results:
dumpe2fs fails to read the image on ppc64
Expected results:
dumpe2fs can well read the image on ppc64, as same as on x86_64
Additional info:
More info will follow