public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
	"Lukáš Czerner" <lczerner@redhat.com>,
	"Dave Chinner" <david@fromorbit.com>,
	"Eric Sandeen" <sandeen@sandeen.net>
Cc: fstests@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: add regression tests for ^extents punch hole
Date: Tue, 24 Feb 2015 19:03:56 -0800	[thread overview]
Message-ID: <20150225030356.GA6880@mew.dhcp4.washington.edu> (raw)
In-Reply-To: <20150224220719.GD4251@dastard> <alpine.LFD.2.00.1502241538430.5931@localhost.localdomain> <20150225002437.GB3782@thunk.org>

On Tue, Feb 24, 2015 at 07:24:37PM -0500, Theodore Ts'o wrote:
> I suspect our current generic fsstress and fsx tests would catch this
> already, and what I need to do is to make sure I add ext3/1k to my
> test configurations (currently I test an ext3 configuration, and a 1k
> block configuration, but I don't currently test ext3/1k together).
> That would probably round out my full test iteration to a very
> pleasing 24 hours or so, which is fine, although I wouldn't want it to
> take much longer than that.
> 
Actually, this issue isn't specific to 1k blocks, so I wouldn't count on
it :) That block size in my tests is an artifact of the initial
reproducer Lukas had (generic/270 on ext3 with 1k blocks). It just so
happens that the start/len arguments fsstress chooses for punch hole
operations in that setup straddles the indirect tree levels in the wrong
ways.


On Tue, Feb 24, 2015 at 03:58:06PM +0100, Lukáš Czerner wrote:
> Omar, can you make the test generic and can this be reproduced on 4k
> block size ? If not, can you make a generic reproducer which does
> not depend on the block size ?
> 
> Also if we want to include the special case for ext4, we need to
> have a function which allows us to alter the mkfs options without
> completely overriding the user specified options. I think that there
> is something like that for xfs, Omar can you do that for ext4 as
> well ?
> 
> Thanks!
> -Lukas
> 
> 
No problem, I'll have a go at it.


On Wed, Feb 25, 2015 at 09:07:19AM +1100, Dave Chinner wrote:
> It's built into the _scratch_mkfs_xfs wrapper, where if the test
> supplies extra options and that conflicts with the CLI supplied
> options it drops the CLI specific options and just uses the test
> options.
> 
> I've mentioned this specificly in the past, too. i.e. that all
> _scratch_mkfs_$FSTYP wrappers should be handling CLI vs test
> specific options like this.... :/
> 
> Cheers,
> 
> Dave.
> 
I'll take that into account.


Thanks, everyone!
-- 
Omar

  reply	other threads:[~2015-02-25  3:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 22:39 [PATCH] ext4: add regression tests for ^extents punch hole Omar Sandoval
2015-02-23 22:46 ` Dave Chinner
2015-02-23 23:11   ` Omar Sandoval
2015-02-23 23:28     ` Eric Sandeen
2015-02-23 23:43       ` Eric Sandeen
2015-02-24 10:11   ` Lukáš Czerner
2015-02-24 11:31     ` Dave Chinner
2015-02-24 11:52       ` Lukáš Czerner
2015-02-24 12:49         ` Dave Chinner
2015-02-24 14:58           ` Lukáš Czerner
2015-02-24 22:07             ` Dave Chinner
2015-02-25  0:24           ` Theodore Ts'o
2015-02-25  3:03             ` Omar Sandoval [this message]
2015-02-25  8:42               ` Lukáš Czerner

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=20150225030356.GA6880@mew.dhcp4.washington.edu \
    --to=osandov@osandov.com \
    --cc=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=tytso@mit.edu \
    /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