From: Dave Chinner <david@fromorbit.com>
To: alexander.tsvetkov@oracle.com
Cc: xfs@oss.sgi.com
Subject: Re: generic/204: correct log size for XFS
Date: Fri, 11 Apr 2014 09:53:22 +1000 [thread overview]
Message-ID: <20140410235322.GA15995@dastard> (raw)
In-Reply-To: <53467259.1080604@oracle.com>
On Thu, Apr 10, 2014 at 02:28:41PM +0400, alexander.tsvetkov@oracle.com wrote:
> generic/204 fails on device with Advanced Format of 4096 bytes per
> physical sector and when partition starts at the 4K boundary/./In this case
> filesystem sector/block size will be of 4096 bytes size and
> _scratch_mkfs_sized
> fails because mkfs reports that 5Mb log size is not enough to create
> a filesystem,
> for example attempt to make filesystem on such partition:
>
> mkfs.xfs -f -bsize=4096 -l size=5m -d size=109051904 /dev/sdb2"
>
> results to:
>
> "log size 1280 blocks too small, minimum size is 1605 blocks"
>
> and generic/204fails with ENOSPC before it has finished creating the
> necessary files:
>
> "QA output created by 204
> ./tests/generic/204: line 86: echo: write error: No space left on device
> ..."
>
> Log size of 7Mbis enough to make filesytem and pass this test.
This is missing a s-o-b line. Can you add one?
>
> diff --git a/tests/generic/204 b/tests/generic/204
> index 13a762a..4ebab26 100755
> --- a/tests/generic/204
> +++ b/tests/generic/204
> @@ -53,9 +53,9 @@ _scratch_mkfs 2> /dev/null | _filter_mkfs 2>
> $tmp.mkfs > /dev/null
>
> # For xfs, we need to handle the different default log sizes that
> different
> # versions of mkfs create. All should be valid with a 5MB log, so
> use that.
> -[ $FSTYP = "xfs" ] && MKFS_OPTIONS="$MKFS_OPTIONS -l size=5m"
> +[ $FSTYP = "xfs" ] && MKFS_OPTIONS="$MKFS_OPTIONS -l size=7m"
>
> -SIZE=`expr 104 \* 1024 \* 1024`
> +SIZE=`expr 106 \* 1024 \* 1024`
> _scratch_mkfs_sized $SIZE $dbsize 2> /dev/null \
> | _filter_mkfs 2> $tmp.mkfs > /dev/null
> _scratch_mount
The change looks fine, but your mailer is line wrapping and
whitespace mangling the patches. Please read
Documentation/SubmittingPatches in the kernel tree for how to do
this correctly. Also, please don't send patches in multipart emails
- turn off html sending so that git am doesn't throw a wobbly over
it...
I've fixed it up this time....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-04-10 23:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 10:28 generic/204: correct log size for XFS alexander.tsvetkov
2014-04-10 23:53 ` 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=20140410235322.GA15995@dastard \
--to=david@fromorbit.com \
--cc=alexander.tsvetkov@oracle.com \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.