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.
DescriptionCarlos Maiolino
2011-03-02 20:19:40 UTC
Description of problem:
Ext4 warnings are printed when a file size on indirect block map is extended to the maximum file size.
How reproducible:
Always
Steps to Reproduce:
1. Create a Ext4FS removing the extent flag:
mkfs.ext4 -O ^extent <device>
2. After mount the FS, run:
dd if=/dev/zero of=<ext4_mountpoint> bs=1 count=0 seek=4402345721856
3. tail /var/log/messages
kernel: EXT4-fs warning (device dm-4): ext4_block_to_path: block 1074791436 > max in inode 12
Actual results:
A Ext4 warning about the file size is showed
Expected results:
Don't show the warning message.
A patch was already proposed:
http://marc.info/?l=linux-ext4&m=129317158212424&w=4
The patch is also attached to the BZ
Comment 4RHEL Program Management
2011-05-13 15:20:17 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2011-1530.html
Description of problem: Ext4 warnings are printed when a file size on indirect block map is extended to the maximum file size. How reproducible: Always Steps to Reproduce: 1. Create a Ext4FS removing the extent flag: mkfs.ext4 -O ^extent <device> 2. After mount the FS, run: dd if=/dev/zero of=<ext4_mountpoint> bs=1 count=0 seek=4402345721856 3. tail /var/log/messages kernel: EXT4-fs warning (device dm-4): ext4_block_to_path: block 1074791436 > max in inode 12 Actual results: A Ext4 warning about the file size is showed Expected results: Don't show the warning message. A patch was already proposed: http://marc.info/?l=linux-ext4&m=129317158212424&w=4 The patch is also attached to the BZ