From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] common/populate: decrease the step of rm file
Date: Wed, 3 Apr 2019 15:43:59 -0700 [thread overview]
Message-ID: <20190403224359.GB32415@magnolia> (raw)
In-Reply-To: <1553759339-2206-1-git-send-email-xuyang2018.jy@cn.fujitsu.com>
On Thu, Mar 28, 2019 at 03:48:59PM +0800, Yang Xu wrote:
> Now that we have allocated 2*4096*64/16(32768) inodes after "Inode btree",
> but the step of rm file is too large to create enough free inodes in agi.
> So the freecount is not enough large to make free_level gt 1 and call
> _scratch__populate on xfs will report the following failure(such as xfs/083):
>
> Failed to create fino of sufficient height!
>
> By decreasing the step of rm file, xfs/083 will pass.
Hmm, what are MOUNT_OPTS and MKFS_OPTIONS when this happens? Are you
running on top of some kind of RAID or 4k sector disk or something?
I think this patch looks ok but I'm puzzled for why a step of
$(ino_per_rec + 1) isn't enough.
--D
> Signed-off-by: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
> ---
> common/populate | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/common/populate b/common/populate
> index 4fa118f0..7403dec3 100644
> --- a/common/populate
> +++ b/common/populate
> @@ -271,7 +271,7 @@ _scratch_xfs_populate() {
> touch "${dir}/${f}"
> done
>
> - seq 0 "$((ino_per_rec + 1))" "${nr}" | while read f; do
> + seq 0 2 "${nr}" | while read f; do
> rm -f "${dir}/${f}"
> done
>
> --
> 2.18.1
>
>
>
next prev parent reply other threads:[~2019-04-03 22:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 7:48 [PATCH] common/populate: decrease the step of rm file Yang Xu
2019-04-01 11:14 ` Eryu Guan
2019-04-03 0:16 ` Darrick J. Wong
2019-04-03 22:43 ` Darrick J. Wong [this message]
2019-04-04 6:30 ` xuyang
2019-04-08 21:57 ` Darrick J. Wong
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=20190403224359.GB32415@magnolia \
--to=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=xuyang2018.jy@cn.fujitsu.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