public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Zorro Lang <zlang@redhat.com>
Cc: Ziyang Zhang <ZiyangZhang@linux.alibaba.com>,
	fstests@vger.kernel.org, linux-xfs@vger.kernel.org,
	hsiangkao@linux.alibaba.com
Subject: Re: [PATCH V5 2/2] common/populate: Ensure that S_IFDIR.FMT_BTREE is in btree format
Date: Sat, 10 Dec 2022 18:30:10 -0800	[thread overview]
Message-ID: <Y5VAss77Xm8JUu4r@magnolia> (raw)
In-Reply-To: <20221210135724.owsxdqiirtkqsv6e@zlang-mailbox>

On Sat, Dec 10, 2022 at 09:57:24PM +0800, Zorro Lang wrote:
> On Fri, Dec 09, 2022 at 08:37:41AM -0800, Darrick J. Wong wrote:
> > On Thu, Dec 08, 2022 at 03:28:43PM +0800, Ziyang Zhang wrote:
> > > Sometimes "$((128 * dblksz / 40))" dirents cannot make sure that
> > > S_IFDIR.FMT_BTREE could become btree format for its DATA fork.
> > > 
> > > Actually we just observed it can fail after apply our inode
> > > extent-to-btree workaround. The root cause is that the kernel may be
> > > too good at allocating consecutive blocks so that the data fork is
> > > still in extents format.
> > > 
> > > Therefore instead of using a fixed number, let's make sure the number
> > > of extents is large enough than (inode size - inode core size) /
> > > sizeof(xfs_bmbt_rec_t).
> > > 
> > > Reviewed-by: Zorro Lang <zlang@redhat.com>
> > > Reviewed-by: Allison Henderson <allison.henderson@oracle.com>
> > > Suggested-by: "Darrick J. Wong" <djwong@kernel.org>
> > > Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
> > > Signed-off-by: Ziyang Zhang <ZiyangZhang@linux.alibaba.com>
> > > ---
> > >  common/populate | 34 +++++++++++++++++++++++++++++++++-
> > >  common/xfs      |  9 +++++++++
> > >  2 files changed, 42 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/common/populate b/common/populate
> > > index 6e004997..0d334a13 100644
> > > --- a/common/populate
> > > +++ b/common/populate
> > > @@ -71,6 +71,37 @@ __populate_create_dir() {
> > >  	done
> > >  }
> > >  
> > > +# Create a large directory and ensure that it's a btree format
> > > +__populate_xfs_create_btree_dir() {
> > > +	local name="$1"
> > > +	local isize="$2"
> > > +	local missing="$3"
> > > +	local icore_size="$(_xfs_inode_core_bytes)"
> > 
> > Doesn't this helper require a path argument now?
> 
> What kind of "path" argument? I think he copy it from __populate_create_dir(),
> and keep using the "name" as the root path to create files/dir.

This path argument, from
https://lore.kernel.org/fstests/20221208072843.1866615-2-ZiyangZhang@linux.alibaba.com/T/#u

+# Number of bytes reserved for only the inode record, excluding the
+# immediate fork areas.
+_xfs_get_inode_core_bytes()
+{
+	local dir="$1"
+
+	if _xfs_has_feature "$dir" crc; then

--D

> > 
> > --D
> > 
> > > +	# We need enough extents to guarantee that the data fork is in
> > > +	# btree format.  Cycling the mount to use xfs_db is too slow, so
> > > +	# watch for when the extent count exceeds the space after the
> > > +	# inode core.
> > > +	local max_nextents="$(((isize - icore_size) / 16))"
> > > +	local nr=0
> > > +
> > > +	mkdir -p "${name}"
> > > +	while true; do
> > > +		local creat=mkdir
> > > +		test "$((nr % 20))" -eq 0 && creat=touch
> > > +		$creat "${name}/$(printf "%.08d" "$nr")"
> > > +		if [ "$((nr % 40))" -eq 0 ]; then
> > > +			local nextents="$(_xfs_get_fsxattr nextents $name)"
> > > +			[ $nextents -gt $max_nextents ] && break
> > > +		fi
> > > +		nr=$((nr+1))
> > > +	done
> > > +
> > > +	test -z "${missing}" && return
> > > +	seq 1 2 "${nr}" | while read d; do
> > > +		rm -rf "${name}/$(printf "%.08d" "$d")"
> > > +	done
> > > +}
> > > +
> > >  # Add a bunch of attrs to a file
> > >  __populate_create_attr() {
> > >  	name="$1"
> > > @@ -176,6 +207,7 @@ _scratch_xfs_populate() {
> > >  
> > >  	blksz="$(stat -f -c '%s' "${SCRATCH_MNT}")"
> > >  	dblksz="$(_xfs_get_dir_blocksize "$SCRATCH_MNT")"
> > > +	isize="$(_xfs_get_inode_size "$SCRATCH_MNT")"
> > >  	crc="$(_xfs_has_feature "$SCRATCH_MNT" crc -v)"
> > >  	if [ $crc -eq 1 ]; then
> > >  		leaf_hdr_size=64
> > > @@ -226,7 +258,7 @@ _scratch_xfs_populate() {
> > >  
> > >  	# - BTREE
> > >  	echo "+ btree dir"
> > > -	__populate_create_dir "${SCRATCH_MNT}/S_IFDIR.FMT_BTREE" "$((128 * dblksz / 40))" true
> > > +	__populate_xfs_create_btree_dir "${SCRATCH_MNT}/S_IFDIR.FMT_BTREE" "$isize" true
> > >  
> > >  	# Symlinks
> > >  	# - FMT_LOCAL
> > > diff --git a/common/xfs b/common/xfs
> > > index 674384a9..7aaa63c7 100644
> > > --- a/common/xfs
> > > +++ b/common/xfs
> > > @@ -1487,6 +1487,15 @@ _require_xfsrestore_xflag()
> > >  			_notrun 'xfsrestore does not support -x flag.'
> > >  }
> > >  
> > > +# Number of bytes reserved for a full inode record, which includes the
> > > +# immediate fork areas.
> > > +_xfs_get_inode_size()
> > > +{
> > > +	local mntpoint="$1"
> > > +
> > > +	$XFS_INFO_PROG "$mntpoint" | sed -n '/meta-data=.*isize/s/^.*isize=\([0-9]*\).*$/\1/p'
> > > +}
> > > +
> > >  # Number of bytes reserved for only the inode record, excluding the
> > >  # immediate fork areas.
> > >  _xfs_get_inode_core_bytes()
> > > -- 
> > > 2.18.4
> > > 
> > 
> 

  reply	other threads:[~2022-12-11  2:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08  7:28 [PATCH V5 0/2] cleanup and bugfix for xfs tests related to btree format Ziyang Zhang
2022-12-08  7:28 ` [PATCH V5 1/2] common/xfs: Add a helper to export inode core size Ziyang Zhang
2022-12-08  7:28 ` [PATCH V5 2/2] common/populate: Ensure that S_IFDIR.FMT_BTREE is in btree format Ziyang Zhang
2022-12-09 16:37   ` Darrick J. Wong
2022-12-10 13:57     ` Zorro Lang
2022-12-11  2:30       ` Darrick J. Wong [this message]
2022-12-11 11:01         ` Zorro Lang
2022-12-11 11:23           ` Zorro Lang
2022-12-11 19:19             ` Darrick J. Wong
2022-12-12  3:43           ` Ziyang Zhang

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=Y5VAss77Xm8JUu4r@magnolia \
    --to=djwong@kernel.org \
    --cc=ZiyangZhang@linux.alibaba.com \
    --cc=fstests@vger.kernel.org \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@redhat.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