From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>, <fstests@vger.kernel.org>,
<eguan@redhat.com>, <fdmanana@gmail.com>
Subject: [PATCH v3] fstests: btrfs: Check if btrfs will create inline-then-regular file extents
Date: Thu, 6 Apr 2017 09:28:53 +0800 [thread overview]
Message-ID: <20170406012853.31414-1-quwenruo@cn.fujitsu.com> (raw)
Btrfs allows inline file extent if and only if
1) It's at offset 0
2) It's smaller than min(max_inline, page_size)
Although we don't specify if the size is before compression or after
compression.
At least according to current behavior, we are only limiting the size
after compression.
3) It's the only file extent
So that if we append existing inline extent, it should be converted
to regular file extents.
However several users in btrfs mail list have reported invalid inline
file extent, which only meets the first two condition, but with regular
file extents following.
The bug is here for a long long time, so long that we have modified
kernel and btrfs-progs to accept such case, but it's still not designed
behavior, and must be detected and fixed.
Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
---
v2:
All suggested by Eryu Guan
Use loop_counts instead of runtime to avoid naming confusion.
Fix whitespace issues
Use fsync instead of sync
Use $XFS_IO_PROG instead of calling xfs_io directly
Always output corruption possibility into seqres.full
v3:
All suggested by Filipe Manana
Fix gramma errors
Use simpler reproducer
Add test case to compress group
---
tests/btrfs/140 | 111 ++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/140.out | 2 +
tests/btrfs/group | 1 +
3 files changed, 114 insertions(+)
create mode 100755 tests/btrfs/140
create mode 100644 tests/btrfs/140.out
diff --git a/tests/btrfs/140 b/tests/btrfs/140
new file mode 100755
index 0000000..183d9cd
--- /dev/null
+++ b/tests/btrfs/140
@@ -0,0 +1,111 @@
+#! /bin/bash
+# FS QA Test 140
+#
+# Check if btrfs will create inline-then-regular file layout.
+#
+# Btrfs only allows inline file extent if file is small enough, and any
+# incoming write enlarges the file beyond max_inline should replace inline
+# extents with regular extents.
+# This is a long standing bug, so fsck won't detect it and kernel will allow
+# normal read on it, but should be avoided.
+#
+#-----------------------------------------------------------------------
+# Copyright (c) 2017 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
+
+# remove previous $seqres.full before test
+rm -f $seqres.full
+
+# real QA test starts here
+
+# Modify as appropriate.
+_supported_fs btrfs
+_supported_os Linux
+_require_scratch
+_require_btrfs_command inspect-internal dump-tree
+
+inline_size=2048
+page_size=$(get_page_size)
+loop_counts=$(($LOAD_FACTOR * 4)) #The possibility is over 80%, just in case
+
+do_test()
+{
+ _scratch_mkfs > /dev/null 2>&1
+
+ # specify max_inline and compress explicitly to create
+ # inlined compressed extent
+ _scratch_mount "-o max_inline=$inline_size,compress"
+
+ # Page sized data will be compressed to quite small size,
+ # which is about 50 bytes for 4K, 100 bytes for 64K,
+ # far smaller than $inline_size, causing a inlined compressed
+ # file extent
+ $XFS_IO_PROG -f -c "pwrite 0 $page_size" -c "fsync" $SCRATCH_MNT/file \
+ > /dev/null 2>&1
+
+ # Append another page to file in snapshot, since its offset is not
+ # 0, it will cause regular extent, and should convert inline extent
+ # to regular too.
+ $XFS_IO_PROG -c "pwrite $page_size $page_size" $SCRATCH_MNT/file \
+ > /dev/null 2>&1
+ _scratch_unmount
+
+ # Fsck won't report inline-then-regular as error, as it's so long
+ # standing that we have no choice but to accept.
+ # So here we use dump-tree to catch inline extent.
+ $BTRFS_UTIL_PROG inspect-internal dump-tree -t 5 $SCRATCH_DEV \
+ > $tmp.dump_tree 2>&1
+ if grep -q inline $tmp.dump_tree; then
+ cat $tmp.dump_tree >> $seqres.full
+ echo "Invalid inline file extent detected"
+ return 1
+ fi
+ return 0
+}
+
+for i in $(seq 1 $loop_counts); do
+ do_test
+ if [ $? -ne 0 ]; then
+ corrupted=$(($corrupted + 1))
+ fi
+done
+
+echo "Corruption possibility: $corrupted/$loop_counts" >> $seqres.full
+echo "Silence is golden"
+
+# success, all done
+status=0
+exit
diff --git a/tests/btrfs/140.out b/tests/btrfs/140.out
new file mode 100644
index 0000000..24e90bc
--- /dev/null
+++ b/tests/btrfs/140.out
@@ -0,0 +1,2 @@
+QA output created by 140
+Silence is golden
diff --git a/tests/btrfs/group b/tests/btrfs/group
index 641d826..2c38fdd 100644
--- a/tests/btrfs/group
+++ b/tests/btrfs/group
@@ -142,3 +142,4 @@
137 auto quick send
138 auto compress
139 auto qgroup
+140 auto compress
--
2.9.3
next reply other threads:[~2017-04-06 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 1:28 Qu Wenruo [this message]
2017-04-06 16:02 ` [PATCH v3] fstests: btrfs: Check if btrfs will create inline-then-regular file extents Filipe Manana
2017-04-07 0:28 ` Qu Wenruo
2017-04-07 9:30 ` Filipe Manana
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170406012853.31414-1-quwenruo@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=eguan@redhat.com \
--cc=fdmanana@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).