From: Dave Chinner <david@fromorbit.com>
To: Andrew Price <anprice@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 3/3] common/rc: support gfs2 in _scratch_mkfs_sized
Date: Tue, 26 May 2015 08:30:50 +1000 [thread overview]
Message-ID: <20150525223050.GV4316@dastard> (raw)
In-Reply-To: <1431697004-3032-3-git-send-email-anprice@redhat.com>
On Fri, May 15, 2015 at 02:36:44PM +0100, Andrew Price wrote:
> This enables tests which use _scratch_mkfs_sized when $FSTYP == gfs2.
> Where tests use a fs size too small to contain a gfs2 fs created with
> default options, specify a smaller journal size to make it fit.
>
> Signed-off-by: Andrew Price <anprice@redhat.com>
....
> diff --git a/tests/generic/015 b/tests/generic/015
> index 8d3fd5f..d1805a7 100755
> --- a/tests/generic/015
> +++ b/tests/generic/015
> @@ -53,6 +53,9 @@ _supported_os IRIX Linux
> _require_scratch
> _require_no_large_scratch_dev
>
> +# GFS2 needs a smaller journal size to fit in 50M
> +[ $FSTYP = "gfs2" ] && MKFS_OPTIONS="$MKFS_OPTIONS -J16"
This belongs in scratch_mkfs_sized(), as gfs2 specific code. You
have the size of the fs to be made there, so set the limit
appropriately there.
As it is, it's worth considering that this is exposing a mkfs.gfs2
bug in that it doesn't handle small filesystem sizes correctly by
default....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2015-05-25 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 13:36 [PATCH 1/3] common/quota: set VFS_QUOTA for gfs2 Andrew Price
2015-05-15 13:36 ` [PATCH 2/3] generic/group: add generic/082 to the quota group Andrew Price
2015-05-15 13:36 ` [PATCH 3/3] common/rc: support gfs2 in _scratch_mkfs_sized Andrew Price
2015-05-25 22:30 ` Dave Chinner [this message]
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=20150525223050.GV4316@dastard \
--to=david@fromorbit.com \
--cc=anprice@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