On Wed, Nov 28, 2012 at 11:49:16PM -0600, Eric Sandeen wrote: > > > > Wow, that was unnecessarily large. Here's a smaller one... > > > > Was that by hand-hackery or did you figure out how to hit > it at runtime? Via hand-hackery. The tst_extents command allow you to do things like this: % ./build/lib/ext2fs/tst_extents -w /tmp/test_case.img tst_extents 1.42.6 (21-Sep-2012) tst_extents: inode <16> header: magic=f30a entries=3 max=4 depth=1 generation=0 Loaded inode 16 tst_extents: root extent: lblk 0--83, len 84, pblk 1731, flags: (none) tst_extents: next_sibling extent: lblk 84--4021, len 3938, pblk 1899, flags: (none) tst_extents: replace_node 80 0 1899 extent replace: 16 extent: lblk 80--79, len 0, pblk 1899, flags: (none) extent: lblk 80--4021, len 3942, pblk 1899, flags: (none) tst_extents: prev_sibling extent: lblk 0--79, len 80, pblk 1731, flags: 2ND_VISIT tst_extents: q - 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
