From: Jan Kara <jack@suse.cz>
To: Dave Chinner <david@fromorbit.com>
Cc: Jan Kara <jack@suse.cz>, xfs@oss.sgi.com
Subject: Re: Test xfs/287 failure
Date: Thu, 2 Oct 2014 09:45:34 +0200 [thread overview]
Message-ID: <20141002074534.GA19748@quack.suse.cz> (raw)
In-Reply-To: <20141001224155.GW4758@dastard>
On Thu 02-10-14 08:41:55, Dave Chinner wrote:
> On Wed, Oct 01, 2014 at 05:23:14PM +0200, Jan Kara wrote:
> > Hello,
> >
> > so after installing latest xfsdump (just pulled git repo at oss.sgi.com),
> > I'm getting failure in test xfs/287. The failure is:
> > xfs/287 2s ... 2s
> > _check_xfs_filesystem: filesystem on /dev/vdb2 is inconsistent (r) (see
> > /var/lib/xfstests/results//xfs/287.full)
> >
> > And the 287.full has:
> > ...
> > Phase 3 - for each AG...
> > - scan (but don't clear) agi unlinked lists...
> > - process known inodes and perform inode discovery...
> > - agno = 0
> > directory flags set on non-directory inode 133
> > directory flags set on non-directory inode 134
> > directory flags set on non-directory inode 133
> > would fix bad flags.
> > directory flags set on non-directory inode 134
> > would fix bad flags.
> > ...
> >
> > Complete file is attached. I'm using also the latest xfsprogs from git and
> > kernel 3.17.0-rc5 (plus couple of my patches but these should have no
> > influence).
>
> It's a bug, but a minor inconvenience at worst. I sent patches to
> fix this a couple of days ago:
>
> http://oss.sgi.com/archives/xfs/2014-09/msg00510.html
Ah, OK. Thanks for info. I was just going through xfstests failures in my
test VM and fixing xfstests / my setup and I wasn't able to figure out this
one...
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-10-02 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 15:23 Test xfs/287 failure Jan Kara
2014-10-01 22:41 ` Dave Chinner
2014-10-02 7:45 ` Jan Kara [this message]
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=20141002074534.GA19748@quack.suse.cz \
--to=jack@suse.cz \
--cc=david@fromorbit.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.