From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: fstests@vger.kernel.org
Subject: Re: question about xfs/122
Date: Fri, 27 May 2016 14:44:48 +0800 [thread overview]
Message-ID: <5747ECE0.6060105@cn.fujitsu.com> (raw)
In-Reply-To: <20160526163249.GA4595@birch.djwong.org>
> On Thu, May 26, 2016 at 03:31:25PM +0800, Xiao Yang wrote:
>> 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.
> The missing fields are for the reflink and rmap btrees. I could say
> to just ignore it, but I don't want to establish a precedent of
> ignoring xfs/122 errors...
>
> I'm wondering if perhaps this test ought to filter out /missing/ lines
> in the test output?
>
> --D
>
Hi Darrick
When i run xfstests test case xfs/122 on RHEL7.2GA with
xfsprog-dev(3.2.2), i will get such error abou xfs/122:
-------------------------------------------------------------------------------------------
-offsetof(xfs_sb_t, sb_agblklog) = 124
-offsetof(xfs_sb_t, sb_agblocks) = 84
-offsetof(xfs_sb_t, sb_agcount) = 88
-offsetof(xfs_sb_t, sb_bad_features2) = 204
-offsetof(xfs_sb_t, sb_blocklog) = 120
-offsetof(xfs_sb_t, sb_blocksize) = 4
-offsetof(xfs_sb_t, sb_crc) = 224
-offsetof(xfs_sb_t, sb_dblocks) = 8
-offsetof(xfs_sb_t, sb_dirblklog) = 192
-offsetof(xfs_sb_t, sb_fdblocks) = 144
-offsetof(xfs_sb_t, sb_features2) = 200
-offsetof(xfs_sb_t, sb_features_compat) = 208
-offsetof(xfs_sb_t, sb_features_incompat) = 216
-offsetof(xfs_sb_t, sb_features_log_incompat) = 220
-offsetof(xfs_sb_t, sb_features_ro_compat) = 212
-offsetof(xfs_sb_t, sb_flags) = 178
-offsetof(xfs_sb_t, sb_fname[12]) = 120
-offsetof(xfs_sb_t, sb_frextents) = 152
-offsetof(xfs_sb_t, sb_gquotino) = 168
-offsetof(xfs_sb_t, sb_icount) = 128
-offsetof(xfs_sb_t, sb_ifree) = 136
-offsetof(xfs_sb_t, sb_imax_pct) = 127
-offsetof(xfs_sb_t, sb_inoalignmt) = 180
......
-sizeof(struct xfs_acl) = 4
-sizeof(struct xfs_acl_entry) = 12
-sizeof(struct xfs_attr3_leaf_hdr) = 80
-sizeof(struct xfs_attr3_leafblock) = 88
-sizeof(struct xfs_attr3_rmt_hdr) = 56
-sizeof(struct xfs_btree_block) = 72
-sizeof(struct xfs_clone_args) = 32
-sizeof(struct xfs_da3_blkinfo) = 56
-sizeof(struct xfs_da3_intnode) = 64
......
-------------------------------------------------------------------------------------------
I think the number of structure is always changing based on different
xfsporg-dev version.
Can we determine whether all expected structure exist in current
enviroment or not by comparing
line number of standard output with line number of actual output? If the
line number of actual
output is less than expeted number of structure, we trust that some
structure is missing and set
test result to not run.
Regards,
Xiao Yang
>> Please advise. Thanks very much.
>>
>> Regards,
>> Xiao Yang
>>
>>
>>
>>
>>
>> _______________________________________________
>> xfs mailing list
>> xfs@oss.sgi.com
>> http://oss.sgi.com/mailman/listinfo/xfs
>
>
next prev parent reply other threads:[~2016-05-27 6:45 UTC|newest]
Thread overview: 32+ 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
[not found] ` <5746A64D.6080309@cn.fujitsu.com>
[not found] ` <20160526163249.GA4595@birch.djwong.org>
2016-05-27 6:33 ` [PATCH] xfs/122: add check number of structure Xiao Yang
2016-05-27 7:28 ` Darrick J. Wong
2016-05-27 7:17 ` [PATCH] xfs/122: filter out reflink and rmap related outputs Xiao Yang
2016-05-27 8:00 ` [PATCH] xfs/122: add check number of structure Xiao Yang
2016-05-27 6:44 ` Xiao Yang [this message]
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
[not found] <57BD53DC.30605@cn.fujitsu.com>
2016-08-24 23:03 ` question about xfs/122 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=5747ECE0.6060105@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--cc=darrick.wong@oracle.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