public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs@oss.sgi.com
Subject: question about xfs/122
Date: Thu, 26 May 2016 15:31:25 +0800	[thread overview]
Message-ID: <5746A64D.6080309@cn.fujitsu.com> (raw)
In-Reply-To: <146424222237.6278.4174636124436241002.stgit@birch.djwong.org>

Hi Darrick

When i run xfstests test case xfs/122 on RHEL7.2GA with xfsprog-dev(4.5.0),
I always get such error about xfs/122:
---------------------------------------------------------
  sizeof(struct xfs_extent_data_info) = 32
  sizeof(struct xfs_fs_eofblocks) = 128
  sizeof(struct xfs_icreate_log) = 28
-sizeof(struct xfs_refcount_key) = 4
-sizeof(struct xfs_refcount_rec) = 12
-sizeof(struct xfs_rmap_key) = 4
-sizeof(struct xfs_rmap_rec) = 24
-sizeof(struct xfs_rmapx_key) = 20
  sizeof(xfs_agf_t) = 224
  sizeof(xfs_agfl_t) = 36
  sizeof(xfs_agi_t) = 336
---------------------------------------------------------

This case can pass with modern xfsprogs(i.e. 4.3+ and all the new v5 stuff) as you said.
Could you tell me which specific version can support this case. In addition, what can be
done to work around this failure.

Please advise. Thanks very much.

Regards,
Xiao Yang





_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2016-05-26  7:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-26  5:57 [PATCH 0/7] xfstests: minor fixes for the reflink/dedupe tests Darrick J. Wong
2016-05-26  5:57 ` [PATCH 1/7] xfs/104: don't enospc when ag metadata overhead grows Darrick J. Wong
2016-05-26  8:08   ` Christoph Hellwig
2016-05-26  5:57 ` [PATCH 2/7] tests: don't put loop control files on the scratch mount Darrick J. Wong
2016-05-26  8:09   ` Christoph Hellwig
2016-05-26 16:07     ` Darrick J. Wong
2016-05-27  3:28   ` [PATCH v2 " Darrick J. Wong
2016-05-31 12:52     ` Christoph Hellwig
2016-05-26  5:57 ` [PATCH 3/7] xfs: test copy-on-write leftover recovery Darrick J. Wong
2016-05-26  8:22   ` Christoph Hellwig
2016-05-26  5:57 ` [PATCH 4/7] xfs: test per-ag allocation accounting during truncate-caused refcountbt expansion Darrick J. Wong
2016-05-26  8:23   ` Christoph Hellwig
2016-05-26  5:57 ` [PATCH 5/7] reflink: test interaction with swap files Darrick J. Wong
2016-05-26  8:24   ` Christoph Hellwig
2016-05-26  5:57 ` [PATCH 6/7] xfs: test rmap behavior when multiple bmbt records map to a single rmapbt record Darrick J. Wong
2016-05-26  8:04   ` Christoph Hellwig
2016-05-26 16:12     ` Darrick J. Wong
2016-05-27  3:28   ` [PATCH v2 " Darrick J. Wong
2016-05-31 12:52     ` Christoph Hellwig
2016-05-26  5:57 ` [PATCH 7/7] reflink: test changing sharers of a block while keeping refcount the same Darrick J. Wong
2016-05-26  8:24   ` Christoph Hellwig
2016-05-26  7:31 ` Xiao Yang [this message]
2016-05-26 16:32   ` question about xfs/122 Darrick J. Wong
2016-05-27 18:02 ` [PATCH 8/7] xfs/122: don't break on old xfsprogs Darrick J. Wong
2016-05-31 12:51   ` Christoph Hellwig
2016-05-31 16:41     ` Darrick J. Wong
2016-05-31 16:43   ` [PATCH v2 " Darrick J. Wong
2016-05-31 19:33     ` Christoph Hellwig

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=5746A64D.6080309@cn.fujitsu.com \
    --to=yangx.jy@cn.fujitsu.com \
    --cc=darrick.wong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox