On Mon, Mar 09, 2009 at 11:13:08AM -0500, Eric Sandeen wrote:
> >> deep-tree-2.img.gz contains an extent tree of depth 4....
> >>
>
> I think this jives w/ what the reporter had, although in the e2image the
> problematic inode only had depth 3 (at the time)
I'm downloading and decompressing the e2image from the reporter right
now. Have you tried mounting the e2image over the loop device with
and without the patch? That should be able to demonstrate the
problem, and then prove that the patch fixes it. I'll also dump out
the extent tree from the reporter and try to create a small test case
based on the inode in question. (Inode #2621457, right?)
- 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
