On 7/9/14, 8:07 PM, Dave Chinner wrote: > Reducing runtime of the test harness is a good idea, but we should > not do that if the cost is that it reduces the reliability of error > detection. Still, this could have a really big impact, especially on filesystems with slow fsck. It'd be great to find a way to make this reliable. It's kind of a historical accident that "test" is always mounted, but "scratch" must be _required. What if we added _require_test if we're going to write to test, and doing so triggers the check? I'm sure there are other ways around it. Spending tons of time in fsck for a filesystem we didn't touch isn't time well spent, IMHO. -Eric -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
