From: Dave Chinner <david@fromorbit.com>
To: harshads <harshads@google.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] ext4/030: Ext4 online resize tests.
Date: Wed, 1 Nov 2017 12:16:47 +1100 [thread overview]
Message-ID: <20171101011647.GC4094@dastard> (raw)
In-Reply-To: <20171101001159.88570-1-harshads@google.com>
On Tue, Oct 31, 2017 at 05:11:59PM -0700, harshads wrote:
> Add tests for Ext4 online resize feature. Once online resizing with
> bigalloc support is merged into Ext4, these tests can be used to
> sanitize the working of that feature. In order to test online resizing
> with bigalloc, set MKFS_OPTIONS="-O bigalloc -C <cluster_size>" and
> run the test.
>
> Signed-off-by: Harshad Shirwadkar <harshads@google.com>
You should do this on a loop device, that way you can test
much bigger sizes and all the critical numbers around 32 bit
overflows in the storage stack (2T, 4T, 8T, 16T, etc). e.g.
see xfs/078.
Also, you should add a test that does grow at ENOSPC will exercising
the fs with fstress. See xfs/104.
Perhaps some of the XFS specific tests in the growfs group could be
turned into generic tests with the right infrastructure, so you get
more coverage on ext4 without a whole lot of extra work...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2017-11-01 1:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 0:11 [PATCH] ext4/030: Ext4 online resize tests harshads
2017-11-01 1:16 ` Dave Chinner [this message]
2017-12-05 3:43 ` [PATCH v2] " harshads
2017-12-05 4:42 ` Eryu Guan
2018-01-04 1:18 ` [PATCH v3] ext4/030: Ext4 online resize with bigalloc tests harshads
2018-01-04 8:09 ` Amir Goldstein
2018-01-04 8:20 ` Eryu Guan
2018-01-05 21:21 ` Harshad Shirwadkar
2018-01-07 15:31 ` Eryu Guan
2018-01-08 2:56 ` Harshad Shirwadkar
2018-01-08 4:18 ` [PATCH v4] " harshads
2018-01-11 7:07 ` Eryu Guan
2018-01-23 5:29 ` Harshad Shirwadkar
2018-01-23 21:53 ` [PATCH v4] ext4: " harshads
2018-01-24 6:37 ` Eryu Guan
2018-01-24 22:58 ` [PATCH v5] " harshads
2018-01-25 5:00 ` 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=20171101011647.GC4094@dastard \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=harshads@google.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