From: David Chinner <dgc@sgi.com>
To: Timothy Shimmin <tes@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>,
asg-qa <asgqa@sgi.com>
Subject: Re: REVIEW XFSQA test out xfs_attr_shortform_bytesfit attr2/attr1 fix
Date: Thu, 10 Apr 2008 15:36:01 +1000 [thread overview]
Message-ID: <20080410053601.GK108924158@sgi.com> (raw)
In-Reply-To: <47FC79FC.5020803@sgi.com>
On Wed, Apr 09, 2008 at 06:10:36PM +1000, Timothy Shimmin wrote:
> Hi there,
>
> A test to test out Eric's fix for xfs_attr_shortform_bytesfit
> bug when going from attr2 to attr1.
>
> With TOT kernel, without patch, one can see the corrupted inline
> dirents. With patch, all is well.
>
> The 186.out _should_ be output'ing ATTR2 for the db version
> command but I'm awaiting Barry's xfsprogs checkin to fix that one -
> and then I will regenerate it.
Really? I'm seeing it fail with ATTR2 in the xfs_db output...
dgc@budgie:~/xfstests$ sudo ./check 186
FSTYP -- xfs (debug)
PLATFORM -- Linux/ia64 budgie 2.6.25-rc3-dgc-xfs
MKFS_OPTIONS -- -f -bsize=4096 /dev/sdb6
MOUNT_OPTIONS -- /dev/sdb6 /mnt/scratch
186 - output mismatch (see 186.out.bad)
13a14
> ATTR2
98a100
> ATTR2
Failures: 186
Failed 1 of 1 tests
dgc@budgie:~/xfstests$
So the first is supposed to be there, but the second shows:
....
=================================
ATTR
ATTR2
core.forkoff = 47
....
Are both supposed to be present?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2008-04-10 5:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 8:10 REVIEW XFSQA test out xfs_attr_shortform_bytesfit attr2/attr1 fix Timothy Shimmin
2008-04-10 5:36 ` David Chinner [this message]
2008-04-14 1:35 ` Timothy Shimmin
2008-04-14 1:46 ` Barry Naujok
2008-04-14 3:22 ` David Chinner
2008-04-14 3:56 ` Timothy Shimmin
2008-04-14 4:23 ` Timothy Shimmin
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=20080410053601.GK108924158@sgi.com \
--to=dgc@sgi.com \
--cc=asgqa@sgi.com \
--cc=tes@sgi.com \
--cc=xfs-dev@sgi.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.