From: Xu Wang <xuw@redhat.com>
To: fstests@vger.kernel.org
Subject: btrfs/010: what's the purpose of test case
Date: Mon, 3 Nov 2014 02:41:04 -0500 (EST) [thread overview]
Message-ID: <707521534.1995887.1415000464631.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <195605038.1993779.1414999815830.JavaMail.zimbra@redhat.com>
Hi,
I run the btrfs/010 for kernel 3.10, the result is failed. When I read the case, I think it may be wrong.
So I post this letter, and wanna to verify it.
The case(btrfs/010) firstly produced a file with some extents in a sub volume, then created 2 snaps of the
sub volume. Then defrag the file in sub volume, and hope the extents numbers are same for sub volume, snap1
and snap2.
The btrfs's snapshot is based on cow, so defrag the original sub volume's file will not affect the file in
snapshot? Am I right?
If I am right, the operation "num_extent_orig=`_extent_count $subvol/foobar`" in btrfs/010 should be before
the defrag operation. And I will send a patch to fix it.
Best regards,
--
George Wang 王旭
Kernel Quantity Engineer
Red Hat Software (Beijing) Co.,Ltd
IRC:xuw
Tel:+86-010-62608041
Phone:15901231579
9/F, Tower C, Raycom
next parent reply other threads:[~2014-11-03 7:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <195605038.1993779.1414999815830.JavaMail.zimbra@redhat.com>
2014-11-03 7:41 ` Xu Wang [this message]
2014-11-03 8:29 ` btrfs/010: what's the purpose of test case Filipe David 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=707521534.1995887.1415000464631.JavaMail.zimbra@redhat.com \
--to=xuw@redhat.com \
--cc=fstests@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