generic/449: always fill up the data device

This is yet another one of those tests that looks at what happens when
we run out of space for more metadata (in this case, xattrs).  Make sure
that the 256M we write to the file to try to stimulate ENOSPC gets
written to the same place that xfs puts xattr data -- the data device.

Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Brian Foster <bfoster@redhat.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
This commit is contained in:
Darrick J. Wong
2021-04-27 21:09:12 -07:00
committed by Eryu Guan
parent e48c1f054f
commit eb8d229ff7
+5
View File
@@ -43,6 +43,11 @@ _require_attrs trusted
_scratch_mkfs_sized $((256 * 1024 * 1024)) >> $seqres.full 2>&1
_scratch_mount || _fail "mount failed"
# This is a test of xattr behavior when we run out of disk space for xattrs,
# so make sure the pwrite goes to the data device and not the rt volume.
test "$FSTYP" = "xfs" && \
$XFS_IO_PROG -c 'chattr -t' $SCRATCH_MNT
TFILE=$SCRATCH_MNT/testfile.$seq
# Create the test file and choose its permissions