Bug 1033548

Summary: [RHEL5] Error : EXT4-fs error (device sda8): ext4_ext_search_left: inode #8126473: (comm db2sysc) ix (60672) != EXT_FIRST_INDEX (0) (depth 1)! leads to DB2 instance to crash
Product: Red Hat Enterprise Linux 5 Reporter: Ludek Smid <lsmid>
Component: e4fsprogsAssignee: Eric Sandeen <esandeen>
Status: CLOSED ERRATA QA Contact: Eryu Guan <eguan>
Severity: high Docs Contact:
Priority: urgent    
Version: 5.11CC: atomlin, djeffery, eguan, ekuric, esandeen, fs-maint, jcastillo, jharriga, jsvarova, kdudka, lmcilroy, lmiksik, mgandhi, plambri, pm-eus, rwheeler, sauchter, sct, spanjikk, vincent
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, the resize4fs utility mishandled the resizing of an ext4 file system to a smaller size. As a consequence, files containing many extents could become corrupted if they were moved during the resize process. With this update, resize4fs now maintains a consistent extent tree when moving files containing many extents, and such files no longer become corrupted in this scenario.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-05 13:21:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1014062    
Bug Blocks: 961026    

Description Ludek Smid 2013-11-22 11:08:33 UTC
This bug has been copied from bug #1014062 and has been proposed
to be backported to 5.10 z-stream (EUS).

Comment 4 Ludek Smid 2013-11-22 11:11:50 UTC
*** Bug 1033201 has been marked as a duplicate of this bug. ***

Comment 5 Eric Sandeen 2013-11-23 02:14:25 UTC
I have this committed in 5.11 and 5.10 now, but for some reason it's not building properly due to the {?dist} tag not expanding properly, AFAICT:

> Could not execute build: e4fsprogs-1.41.12-4.el5 has already been built

Looking into it, should have it built soon.

Comment 9 errata-xmlrpc 2013-12-05 13:21:37 UTC
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/RHBA-2013-1789.html