This is another corruption, found late by the extensive resizing that livecd-creator was doing on Rawhide. From my upstream patch submission: http://marc.info/?l=linux-ext4&m=124699503718719&w=2 --- Commit 53422e8a5644e22ea3f6e0efba82a765b72e4308 moved the new extent insertion in ext2fs_extent_set_bmap prior to the modification of the original extent, but the insert function left the handle pointing a the new extent; this left us modifying the -new- extent not the original one, and winding up with a corrupt extent tree something like: BLOCKS: (0-1):588791-588792, (0):588791 We need to move back to the previous extent prior to modification, if we inserted a new one. --- This could be a problem during resize, or during fsck, and should probably be fixed as I don't think we can work around it. Sorry for all the respins & exceptions these days, I guess ext4 has a few bugs left after all .... (Note: e4fsprogs is still in tech preview)
Built & tagged in e4fsprogs-1.41.5-3
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1413.html