Red Hat Bugzilla – Bug 593133
e2fsprogs: upstream fixes - rebase to 1.41.12
Last modified: 2010-11-10 15:20:45 EST
A few upstream fixes would be good to get into e2fsprogs pre-beta.
e2fsck: mark sparse journal as invalid
e2fsck: make block counting variable in pass1 64 bits
Revert "e2fsck: fix spurious complaints about i_size caused by preallocated blocks" (rhel6 kernel now has support for this)
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Looking more closely at the fixes since 1.41.10 (the current version in RHEL6), it's really -all- bugfixes, plus translation updates.
Rather than cherry picking commits, I think it would be best to just rebase at this point, if that's acceptable.
I don't know if I should set flags back to ? ... I'll wait for some response on this.
Created attachment 414953 [details]
List of commits since 1.41.10
Just to be clear about it, I'm going to reset flags to ? to get explicit approval.
*** Bug 548787 has been marked as a duplicate of this bug. ***
There was one thinko in this release that needs to be fixed straight-off, I'm going to just use this bug to fix it without delay.
From: Eric Sandeen <firstname.lastname@example.org>
Date: Wed, 19 May 2010 18:20:13 +0000 (-0500)
Subject: e2fsck: correct test for EOFBLOCKS
e2fsck: correct test for EOFBLOCKS
This test, added to e2fsprogs-1.41.12, is backwards.
If EOFBLOCKS is set, then the size -should- be less than
the last physical block...
xfstests 013 caught this.
Signed-off-by: Eric Sandeen <email@example.com>
Signed-off-by: Theodore Ts'o <firstname.lastname@example.org>
Built in e2fsprogs-1.41.12-2.el6
*** Bug 562936 has been marked as a duplicate of this bug. ***
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.