> > Unfortunately this is one of those bugs that I can't find a way to > > reproduce except by randomly breaking one fs after another. This > > happens with ext3 and ext4, but so far I haven't seen it happen > > with ext2. > > > > > > *** seed 270, ext3, 2.6.27-rc3 *** > > *** seed 451, ext4, 2.6.27-rc5 *** Given these seed numbers, I assume this was generating using some tool like fsfuzzer? Would it be possible to generate a filesystem image *before* that triggers the problem case, before trying to execute the rm -rf? That would be the fastest way to try to track the problem down. - 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
