linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] fstests: common: Make _test_mount to include MOUNT_OPTIONS to allow consistent _test_cycle_mount
Date: Wed, 24 May 2017 17:22:54 +0800	[thread overview]
Message-ID: <20170524092254.GL7250@eguan.usersys.redhat.com> (raw)
In-Reply-To: <05c560e7-342b-0935-ae38-055e2f40b75e@cn.fujitsu.com>

On Wed, May 24, 2017 at 03:58:11PM +0800, Qu Wenruo wrote:
> 
> 
> At 05/24/2017 01:16 PM, Qu Wenruo wrote:
> > 
> > 
> > At 05/24/2017 01:08 PM, Eryu Guan wrote:
> > > On Wed, May 24, 2017 at 12:28:34PM +0800, Qu Wenruo wrote:
> > > > 
> > > > 
> > > > At 05/24/2017 12:24 PM, Eryu Guan wrote:
> > > > > On Wed, May 24, 2017 at 08:22:25AM +0800, Qu Wenruo wrote:
> > > > > > 
> > > > > > 
> > > > > > At 05/23/2017 07:13 PM, Eryu Guan wrote:
> > > > > > > On Tue, May 23, 2017 at 04:02:05PM +0800, Qu Wenruo wrote:
> > > > > > > > [BUG]
> > > > > > > > If using MOUNT_OPTIONS="-o nodatasum" and btrfs to run genierc/142
> > > > > > > > generic/143 and generic/154, it will cause false alert like:
> > > > > > > > cp: failed to clone '/mnt/test/test-154/file2'
> > > > > > > > from '/mnt/test/test-154/file1': Invalid
> > > > > > > > argument
> > > > > > > 
> > > > > > > MOUNT_OPTIONS is for scratch mount, and
> > > > > > > TEST_FS_MOUNT_OPTS is for test
> > > > > > > dev mount, so I think setting TEST_FS_MOUNT_OPTS to "-o nodatasum"
> > > > > > > should fix your problem.
> > > > > > 
> > > > > > Nope, the problem is the inconsistent of TEST_MNT setup.
> > > > > 
> > > > > It does fix the failure for me, did I miss anything?
> > > > > 
> > > > > # MOUNT_OPTIONS="-o nodatasum" TEST_FS_MOUNT_OPTS="-o
> > > > > nodatasum" ./check generic/142 generic/143 generic/154
> > > > > FSTYP         -- btrfs
> > > > > PLATFORM      -- Linux/x86_64 dhcp-66-86-11 4.12.0-rc1
> > > > > MKFS_OPTIONS  -- /dev/sda6
> > > > > MOUNT_OPTIONS -- -o nodatasum -o
> > > > > context=system_u:object_r:root_t:s0 /dev/sda6
> > > > > /mnt/testarea/scratch
> > > > > 
> > > > > generic/142 2s ... 1s
> > > > > generic/143      18s
> > > > > generic/154      1s
> > > > > Ran: generic/142 generic/143 generic/154
> > > > > Passed all 3 tests
> > > > > 
> > > > 
> > > > But if you only export MOUNT_OPTIONS, it will fail, due to the different
> > > > mount options between test_cycle_mount().
> > > 
> > > That's correct. Sorry, I didn't make it clear in my first reply. I meant
> > > that you should set both TEST_FS_MOUNT_OPTS and MOUNT_OPTIONS to
> > > "-onodatasum", for both test dev and scratch dev.
> > 
> > That's just a workaround, not a root fix.
> > 
> > Not to mention quite a lot test cases lose its coverage.
> > As after _test_cycle_mount(), they are just testing default mount option.
> > 
> > > 
> > > > 
> > > > To make it clear:
> > > > If test mount follows TEST_FS_MOUNT_OPTS, then both the first mount and
> > > > test_cycle_mount should follow TEST_FS_MOUNT_OPTS.
> > > 
> > > _test_mount does follow TEST_FS_MOUNT_OPTS, not MOUNT_OPTIONS, no matter
> > > which mount it is.
> > 
> > While test mount setup by check script follows MOUNT_OPTIONS.
> 
> Well, $MOUNT_OPTIONS is appended by check_generic_filsystem() or
> check_btrfs_filesystem() for btrfs.

Yeah, you're right, I found it too. The _check_<fs>_filesystem() mounts
with MOUNT_OPTIONS unconditionally.

> 
> Which will remount the device with $MOUNT_OPTIONS.
> Further more, this function doesn't care if it's scratch device or test
> device, just use MOUNT_OPTIONS.
> 
> So either we split it for scratch and test device, and follows different
> mount options,
> or just like my submitted patch, to make _test_mount() to follow
> MOUNT_OPTIONS.

Fixing _check_<fs>_filesystem() is the correct way. And I guess we can
refactor out a common function and call it in
_check_[xfs|btrfs|generic]_filesystem.

Thanks for looking into this!

Eryu

> 
> Thanks,
> Qu
> 
> > 
> > Just check the following very basic test script:
> > ------
> > #! /bin/bash
> > # FS QA Test 010
> > #
> > # what am I here for?
> > #
> > 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 generic
> > _supported_os Linux
> > _require_test
> > 
> > mount > $tmp.mount1
> > _test_cycle_mount
> > mount > $tmp.mount2
> > 
> > diff  $tmp.mount1 $tmp.mount2
> > 
> > echo "Silence is golden"
> > # success, all done
> > status=0
> > exit
> > 
> > ------
> > 
> > Thanks,
> > Qu
> > > 
> > > Thanks,
> > > Eryu
> > > -- 
> > > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > > 
> > > 
> 
> 

  reply	other threads:[~2017-05-24  9:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23  8:02 [PATCH] fstests: common: Make _test_mount to include MOUNT_OPTIONS to allow consistent _test_cycle_mount Qu Wenruo
2017-05-23 11:13 ` Eryu Guan
2017-05-24  0:22   ` Qu Wenruo
2017-05-24  4:24     ` Eryu Guan
2017-05-24  4:28       ` Qu Wenruo
2017-05-24  5:08         ` Eryu Guan
2017-05-24  5:16           ` Qu Wenruo
2017-05-24  7:58             ` Qu Wenruo
2017-05-24  9:22               ` Eryu Guan [this message]
2017-05-24  9:27                 ` Qu Wenruo
2017-05-25  3:26                   ` Eryu Guan

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=20170524092254.GL7250@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo@cn.fujitsu.com \
    /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).