On Fri, May 25, 2012 at 02:43:53PM -0500, Eric Sandeen wrote: > Well, this took way too long to find, in retrospect. > > In short, for a completely full filesystem with more than 2^32 > blocks, the rbtree bitmap backend can assemble an extent of used > blocks which is longer than 2^32. If it does, it will overflow > ->count, and corrupt the rbtree for the bitmaps. > > Discovered by completely filling a 32T filesystem using fallocate, and > then observing debugfs, dumpe2fs, and e2fsck all behaving badly. > > (Note that filling with only 31 x 1T files did not show the problem, > because freespace was fragmented enough that there was no sufficiently > long range of used blocks.) > > Signed-off-by: Eric Sandeen <sandeen@xxxxxxxxxx> Thanks, applied. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
