Re: [PATCH v2] generic: check whether we can truncate heavily reflinked file

[Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>]

hi,

On 09/22/2016 02:18 PM, Darrick J. Wong wrote:
> On Thu, Sep 22, 2016 at 10:13:08AM +0800, Wang Xiaoguang wrote:
>> In btrfs, there is a bug about btrfs' truncate codes, it'll leak
>> some fs space as the truncate operation proceeds. If this truncate
>> operation is very large, later metadata request in this truncate
>> operation may fail for enospc error. I also have sent a kernel
>> patch fot btrfs to fix this issue.
>>
>> Signed-off-by: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
>> ---
>>   tests/generic/379     | 86 +++++++++++++++++++++++++++++++++++++++++++++++++++
>>   tests/generic/379.out |  2 ++
>>   tests/generic/group   |  1 +
>>   3 files changed, 89 insertions(+)
>>   create mode 100755 tests/generic/379
>>   create mode 100644 tests/generic/379.out
>>
>> diff --git a/tests/generic/379 b/tests/generic/379
>> new file mode 100755
>> index 0000000..3d2918a
>> --- /dev/null
>> +++ b/tests/generic/379
>> @@ -0,0 +1,86 @@
>> +#! /bin/bash
>> +# FS QA Test 379
>> +#
>> +# Create a heavily reflinked file, then check whether we can truncate
>> +# it correctly.
>> +#
>> +#-----------------------------------------------------------------------
>> +# Copyright (c) 2016 Fujitsu.  All Rights Reserved.
>> +#
>> +# This program is free software; you can redistribute it and/or
>> +# modify it under the terms of the GNU General Public License as
>> +# published by the Free Software Foundation.
>> +#
>> +# This program is distributed in the hope that it would be useful,
>> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
>> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>> +# GNU General Public License for more details.
>> +#
>> +# You should have received a copy of the GNU General Public License
>> +# along with this program; if not, write the Free Software Foundation,
>> +# Inc.,  51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
>> +#-----------------------------------------------------------------------
>> +#
>> +
>> +seq=`basename $0`
>> +seqres=$RESULT_DIR/$seq
>> +echo "QA output created by $seq"
>> +
>> +here=`pwd`
>> +tmp=/tmp/$$
>> +status=1	# failure is the default!
>> +trap "_cleanup; exit \$status" 0 1 2 3 15
>> +
>> +_cleanup()
>> +{
>> +	cd /
>> +	rm -f $tmp.*
>> +}
>> +
>> +# get standard environment, filters and checks
>> +. ./common/rc
>> +. ./common/filter
>> +. ./common/reflink
>> +
>> +# remove previous $seqres.full before test
>> +rm -f $seqres.full
>> +
>> +# Modify as appropriate.
>> +_supported_fs generic
>> +_supported_os Linux
>> +_require_scratch
>> +_require_scratch_reflink
>> +
>> +_scratch_mkfs_sized $((32 * 1024 * 1024)) >> $seqres.full 2>&1
>> +_scratch_mount
>> +
>> +testfile=$SCRATCH_MNT/testfile
>> +dummyfile1=$SCRATCH_MNT/dummyfile1
>> +dummyfile2=$SCRATCH_MNT/dummyfile2
>> +blocksize=$((128 * 1024))
>> +
>> +# create two dummy files, which is used to occupy some fs space first.
>> +_pwrite_byte 0xcdcdcdcd 0 $((8 * 1024 * 1024)) $dummyfile1 > /dev/null
>> +_pwrite_byte 0xcdcdcdcd 0 $((1 * 1024 * 1024)) $dummyfile2 > /dev/null
>> +_pwrite_byte 0xcdcdcdcd 0 $blocksize  $testfile > /dev/null
>> +
>> +echo "Silence is golden"
>> +# try to do reflink unless we get enospc error.
>> +i=1
>> +while true; do
>> +	_reflink_range $testfile 0 $testfile $(($i * $blocksize)) $blocksize \
>> +		2>&1 | grep -q "No space left on device"
>> +	if [ $? -eq 0 ]; then
>> +		break
>> +	fi
>> +	i=$((i + 1))
>> +done
> So, uh... I ran this test on XFS, during which I observed that this loop
> was only eating space at a rate of about 3KB/s.  The created FS is 18MB and
> 12 of that is used by the dummy files, so that means it'll take about an
> hour to run?
>
> (I guess you didn't put it in the 'quick' group, good.)
>
> The file got to be about 16GB in length before I got impatient and killed it.
> Is this expected for this test?
Sorry, I didn't run this test in xfs, I had thought it would take 
several minutes
for xfs. I'll update new version patch according to Eryu's suggestions.

Regards,
Xiaoguang Wang

>
> --D
>
>> +# fs is almost full now and fs internal operations may need some free space,
>> +# for example, in btrfs, transaction will need to reserve space first, so here
>> +# free 1MB space.
>> +rm -rf $dummyfile2
>> +$XFS_IO_PROG -f -c "truncate 0" $testfile
>> +
>> +status=0
>> +exit
>> diff --git a/tests/generic/379.out b/tests/generic/379.out
>> new file mode 100644
>> index 0000000..ec12148
>> --- /dev/null
>> +++ b/tests/generic/379.out
>> @@ -0,0 +1,2 @@
>> +QA output created by 379
>> +Silence is golden
>> diff --git a/tests/generic/group b/tests/generic/group
>> index a602b01..73fce91 100644
>> --- a/tests/generic/group
>> +++ b/tests/generic/group
>> @@ -381,3 +381,4 @@
>>   376 auto quick metadata
>>   377 attr auto quick metadata
>>   378 auto quick metadata
>> +379 auto clone
>> -- 
>> 2.9.0
>>
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe fstests" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>