On Wed, Oct 19, 2011 at 02:29:48PM +0400, Dmitry Monakhov wrote: > During stress testing we want to cover as much code paths as possible > fsstress is very good for this purpose. But it has expandable nature > (disk usage almost continually grow). So once it goes in no ENOSPC > condition it will be where till the end. But by running 'dd' writers > in parallel we can regularly trigger ENOSPC but only for a limited > periods of time because each time it opens file with O_TRUNC. Looks good, but please use a more useful subject line, e.g. xfstests: add a new test that runs fsstress under ENOSPC conditions. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
