On Fri, Oct 14, 2016 at 11:13:02AM -0700, Darrick J. Wong wrote:
> We re-added the UNSHARE flag to fallocate, so go make sure that all
> the unshare tests actually check that the xfs_io falloc command
> supports that flag.

We'll need to improve _require_xfs_io_command to actually run the
command for this to work, otherwise this will fail if the fs supports
reflink but not unshared once xfs_io supports -u.

The poster child would be btrfs, and I would have added some output
here if btrfs support in xfstests wasn't completely broken at this

Well, added Ccs and some output anyway in this case..

root@testvm:~/xfstests# mkfs.btrfs -f /dev/vdb
Btrfs v3.17
See http://btrfs.wiki.kernel.org for more information.

Turning ON incompat feature 'extref': increased hardlink limit per file
to 65536
[  243.592803] BTRFS: device fsid 364c6d95-eaae-43c9-b6bd-139e86206519
devid 1 transid 3 /dev/vdb
fs created label (null) on /dev/vdb
        nodesize 16384 leafsize 16384 sectorsize 4096 size 10.00GiB
root@testvm:~/xfstests# ./check -g quick
[  246.101606] BTRFS info (device vdb): disk space caching is enabled
[  246.102260] BTRFS info (device vdb): flagging fs with big metadata
[  246.106123] BTRFS info (device vdb): creating UUID tree
FSTYP         -- btrfs
PLATFORM      -- Linux/x86_64 testvm 4.8.0+
MKFS_OPTIONS  -- /dev/vdb
MOUNT_OPTIONS -- /dev/vdb /mnt/scratch

our local _scratch_mkfs routine ...
Error: /dev/vdb is mounted
check: failed to mkfs $SCRATCH_DEV using specified options
Passed all 0 tests
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to