Description of problem: Current version of e2fsprogs that is available for F18 has a bug that has been fixed in the most current release of e2fsprogs (1.42.7) Version-Release number of selected component (if applicable): e2fsprogs.x86_64 1.42.5-1.fc18 How reproducible: Create a big filesystem and run e2freefrag Steps to Reproduce: 1. Create a large filesystem (mine is 33TB) 2. Run e2freefrag on said filesystem 3. Actual results: /dev/sdl1: Filesystem too large to use legacy bitmaps while reading block bitmap Expected results: Some filesystem information Additional info: Please see e2fsprogs release notes at: http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.42.7
fixed by: commit ea2d3788621cec5ed067280c7d228ec8897d2208 Author: Theodore Ts'o <tytso> Date: Thu Oct 4 23:30:23 2012 -0400 e2freefrag: use 64-bit rbtree bitmaps Enable the use of 64-bit bitmaps, so e2freefrag will work on file systems with the 64-bit feature enabled. In addition, enable the rbtree-based bitmaps, which significantly saves the amount of memory required (from 97 megs to 1.7 megs for an empty 3T file system) at the cost of additional CPU overhead (but we will claw back some of the additional CPU overhead in the next commit). Addresses-Google-Bug: 7269948 Signed-off-by: "Theodore Ts'o" <tytso> in 1.42.7, as you mentioned. TBH I didn't realize F18 had such an old-ish e2fsprogs.
Sorry, just going to close this CURRENTRELEASE - e2freefrag is informational so not overly critical, and it is fixed now in F19. If you _really_ need it in F18, please let me know.