On v4/512b and v5/1k xfs, there're not enough free inodes for new files and generic/204 fails because of running out of inode not space. Adding "-i maxpct=50" to MKFS_OPTIONS to bump up the inode limit at mkfs time, and test could pass on all configurations. Suggested-by: Dave Chinner <dchinner@xxxxxxxxxx> Signed-off-by: Eryu Guan <eguan@xxxxxxxxxx> --- tests/generic/204 | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/tests/generic/204 b/tests/generic/204 index 13069d8..42985ab 100755 --- a/tests/generic/204 +++ b/tests/generic/204 @@ -52,8 +52,10 @@ _scratch_mkfs 2> /dev/null | _filter_mkfs 2> $tmp.mkfs > /dev/null . $tmp.mkfs # For xfs, we need to handle the different default log sizes that different -# versions of mkfs create. All should be valid with a 5MB log, so use that. -[ $FSTYP = "xfs" ] && MKFS_OPTIONS="$MKFS_OPTIONS -l size=7m" +# versions of mkfs create. All should be valid with a 7MB log, so use that. +# And v4/512 v5/1k xfs don't have enough free inodes, set imaxpct=50 at mkfs +# time solves this problem. +[ $FSTYP = "xfs" ] && MKFS_OPTIONS="$MKFS_OPTIONS -l size=7m -i maxpct=50" SIZE=`expr 106 \* 1024 \* 1024` _scratch_mkfs_sized $SIZE $dbsize 2> /dev/null \ -- 1.8.3.1 _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
