public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <guaneryu@gmail.com>
To: Chandan Rajendra <chandan@linux.vnet.ibm.com>,
	Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH V4 00/20] Fix tests to work on non-4k block sized fs instances
Date: Sun, 23 Sep 2018 00:24:02 +0800	[thread overview]
Message-ID: <20180922162402.GD17817@desktop> (raw)
In-Reply-To: <20180920093358.GO8382@dhcp-12-152.nay.redhat.com>

On Thu, Sep 20, 2018 at 05:33:58PM +0800, Zorro Lang wrote:
> On Wed, Sep 19, 2018 at 05:30:33PM +0530, Chandan Rajendra wrote:
> > This patchset fixes tests (mostly XFS specific ones) to work on
> > variable block size. These patches now use the output of "od" utility
> > to verify the contents of the test files instead of the md5sum
> > utility.
> > 
> > Also, The patchset modifies _filter_fiemap() filter function to
> > optionally print the file offset range in block size units.
> > 
> > Changelog:
> > V3->V4:
> > 1. The following tests now use _get_file_block_size() function to obtain the
> >    underlying filesystem's block size.
> >    xfs/009
> >    xfs/074
> >    xfs/139
> >    xfs/140
> >    xfs/299
> >    generic/018
> >    generic/177
> >    generic/130
> > 2. xfs/139 now creates a scratch filesystem with AG size of 8192 filesystem
> >    blocks instead of the previously used 4400 filesystem blocks.
> > 3. xfs/050 has now been fixed to work with 512 byte sized filesystem blocks.
> >    The "block soft" limit and "block hard" limit values have been increased to
> >    enable the user to have enough blocks in quota to be able to create the
> >    required test files when using 512 byte filesystem blocks.
> 
> Hi,
> 
> Test passed on 512b XFS this time [1]. BTW:
>  - xfs 64k blocksize test PASS
>  - xfs default blocksize test PASS
>  - ext4 64k blocksize test PASS
>  - ext4 default blocksize test PASS

Thanks a lot for testing, Zorro!!

As I don't have access to hardware that supports 64k page, so I only
tested them on x86_64 hardware. I tested all explicitly modified cases
and all cases use _filter_fiemap helper, with test matrix 4k/2k/1k/512 x
v4/v5/reflink/rmapbt on xfs, 4k/2k/1k on ext4 and btrfs. I also hit some
other failures that we need to look into.

xfs/299 fails (and only fails) on 1k block size xfs with reflink or
rmapbt feature enabled. e.g.

 *** push past the hard inode limit (expect EDQUOT)
 [ROOT] 0 0 0 00 [--------] 3 0 0 00 [--------] 0 0 0 00 [--------]
-[NAME] 35 25 125 00 [7 days] 9 4 10 00 [7 days] 0 0 0 00 [--------]
+[NAME] 35 25 125 00 [7 days] 6 4 10 00 [7 days] 0 0 0 00 [--------]
 
 *** push past the hard block limit (expect EDQUOT)
 [ROOT] 0 0 0 00 [--------] 3 0 0 00 [--------] 0 0 0 00 [--------]
-[NAME] =OK= 25 125 0 [7 days] 9 4 10 00 [7 days] 0 0 0 00 [--------]
+[NAME] =OK= 25 125 0 [7 days] 6 4 10 00 [7 days] 0 0 0 00 [--------]
...

And generic/473 fails on xfs with all test combinations. e.g. the diff on 4k
block size v4 xfs

     1: [256..287]: hole
     Hole + Data
     0: [0..127]: hole
    -1: [128..255]: data
    +1: [128..135]: data
     Hole + Data + Hole
     0: [0..127]: hole

Thanks,
Eryu

  reply	other threads:[~2018-09-22 22:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19 12:00 [PATCH V4 00/20] Fix tests to work on non-4k block sized fs instances Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 01/20] Fix xfs/009 to work with 64k block size Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 02/20] xfs/050: Fix "Push past soft inode limit" case Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 03/20] Fix xfs/050 to work with 64k block size Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 04/20] Fix xfs/074 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 05/20] Fix xfs/127 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 06/20] Fix xfs/139 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 07/20] Fix xfs/140 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 08/20] Fix xfs/190 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 09/20] xfs/299: Fix "Push past soft inode limit" case Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 10/20] Fix xfs/299 to work with 64k block size Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 11/20] xfs/325: Inject free_extent error after CoW operation Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 12/20] Fix generic/102 to work with 64k block size Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 13/20] Fix generic/172 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 14/20] Filter fiemap output by FS " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 15/20] Fix generic/177 to work with 64k " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 16/20] Fix generic/230 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 17/20] Fix generic/235 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 18/20] Fix generic/459 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 19/20] Fix generic/018 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 20/20] Fix generic/108 " Chandan Rajendra
2018-09-20  9:33 ` [PATCH V4 00/20] Fix tests to work on non-4k block sized fs instances Zorro Lang
2018-09-22 16:24   ` Eryu Guan [this message]
2018-09-24 10:04     ` Chandan Rajendra
2018-09-24 14:19       ` 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=20180922162402.GD17817@desktop \
    --to=guaneryu@gmail.com \
    --cc=chandan@linux.vnet.ibm.com \
    --cc=fstests@vger.kernel.org \
    --cc=zlang@redhat.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