On Fri, Jan 20, 2017 at 07:55:17PM +0800, Eryu Guan wrote: > Hi all, > > I've seen the warning in subject a few times while testing XFS with > xfstests, with different test configs, different arches, and multiple > tests could trigger the warning, e.g. generic/269 generic/388 xfs/297. > > Today I reproduced it manually by running xfs/297 in a loop on one of my > test hosts, the warning usueally fires within 30 iterations for me. That probaly means we managed to get a delayed allocation still in place when doing direct I/O, which implies the flushing code is racy. I'll try to find some time to debug this further. -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
