On Tue, Mar 12, 2013 at 09:28:54AM +0100, Sander wrote: > Markus Trippelsdorf wrote (ao): > > On 2013.03.11 at 16:37 -0400, Theodore Ts'o wrote: > > > We actually run fsx in a number of different configruations as part of > > > our regression testing before we send Linus a pull request, and > > > haven't found any issues. So unless it's a hardware problem, it seems > > > unlikely to me that your running fsx would turn up anything. > > > > Yes, I let it run for a while anyway and it didn't report any failure. > > > Please note that my local rtorrent version was configured with > > "--with-posix-fallocate". > > Would it be possible to enhance fsx to detect such an issue? fsx in xfstests already uses fallocate() for preallocation and hole punching, so such problems related to these operations can be found using fsx. The issue here, however, involves memory reclaim interactions and so is not something fsx can reproduce in isolation. :/ Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- 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
