Description of problem: On a short O_DIRECT write --- for example, when a large write is submitted but the fs fills up halfway through --- disk blocks get allocated but the file's i_size is not updated. This leads e2fsck to conclude that i_size is wrong on a subsequent fsck. Version-Release number of selected component (if applicable): kernel-2.6.9-5.EL Steps to Reproduce: 1. write 1MB blocks with O_DIRECT until the fs fills up 2. fsck Actual results: Pass 1: Checking inodes, blocks, and sizes Inode 12, i_size is 1889019101184, should be 1889019604992. Fix? yes Expected results: clean fsck. Not massively urgent --- it's really just a cosmetic issue --- but I'm opening the bugzilla so it doesn't get forgotten about completely.
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. Please See https://access.redhat.com/support/policy/updates/errata/ If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.