On Wed, Jun 07, 2017 at 11:08:01AM +0800, Eryu Guan wrote: > On Tue, Jun 06, 2017 at 05:03:05PM -0700, Omar Sandoval wrote: > > On Sat, Jun 03, 2017 at 12:37:00AM -0700, Christoph Hellwig wrote: > > > This looks like a btrfs-specific test, and not like a generic one > > > to me. > > > > Nothing about the workload itself is btrfs-specific, we just have the > > extra check at the end. But I don't really care, I can make it a btrfs > > test unless Eryu has already applied it. > > What's not very clear to me is that how do we check the accountings for > non-btrfs filesystems, i.e. what would cause a test failure on non-btrfs > filesystems besides an xfs_io write failure? I'd prefer a btrfs-specific > test if there's no good way to do the check. Or if we want to keep it a > generic test, some comments on the non-btrfs case would be good. I'm > fine with either way. > > Thanks, > Eryu The only thing I can imagine other filesystems hitting would be an early enospc or some sort of kernel warning, so I'll resend it as a btrfs test. -- 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
