On Thu, May 10, 2018 at 08:13:03AM -0700, Darrick J. Wong wrote: > I ran xfstests on this for fun last night but hung in g/095: > > FSTYP -- xfs (debug) > PLATFORM -- Linux/x86_64 submarine-djwong-mtr01 4.17.0-rc4-djw > MKFS_OPTIONS -- -f -m reflink=1,rmapbt=1, -i sparse=1, -b size=1024, /dev/sdf > MOUNT_OPTIONS -- /dev/sdf /opt > > FWIW the stock v4 and the 'v5 with everything and 4k blocks' vms > passed, so I guess there's a bug somewhere in the sub-page block size > code paths... I haven't seen that in my -b size 1024 -m relink test I'll try your above exact setup, too. Is this disk or SSD? How much memory and how many CPUs? Btw, I think the series might be worthwhile even if we have to delay the sub-page blocksize support - the blocksize == pagesize code is basically entirely separate and already very useful. Only the last three patches contain the small blocksize support, without that we'll just continue using buffer heads for that case for now. -- 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
