public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Ajeet Yadav <ajeet.yadav.77@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfstests 013 - 2.6.35.11 - hang
Date: Wed, 27 Apr 2011 13:11:07 -0400	[thread overview]
Message-ID: <20110427171107.GA29196@infradead.org> (raw)
In-Reply-To: <BANLkTimAXUtO=oxmLUaHLaRBnGafGP-9kg@mail.gmail.com>

On Wed, Apr 27, 2011 at 12:47:57PM +0530, Ajeet Yadav wrote:
> I have downloaded xfstests-fa83948599dd10078a62acab8b0c1f93c82ad807.tar.gz
> Build and run xfstests on MIPS target. This is my first try with
> xfstests but report is not good.

> --- 001.out     Thu Jan  1 00:07:48 1970
> +++ 001.out.bad Thu Jan  1 00:59:07 1970
> @@ -1,9 +1,77 @@
>  QA output created by 001
>  cleanup
>  setup ....................................
> -iter 1 chain ... check ....................................
> -iter 2 chain ... check ....................................
> -iter 3 chain ... check ....................................
> -iter 4 chain ... check ....................................
> -iter 5 chain ... check ....................................
> -cleanup
> +iter 1 chain ... check
> +Error: corruption for small ...

001 tests trivial fail copies, and if these already fail you're
most likely having cache coherency issues.  What mips platform
is this, and do you use any non-mainline patches?

Does 001 also fail for say ext2 and ext3?

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

  reply	other threads:[~2011-04-27 17:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27  7:17 xfstests 013 - 2.6.35.11 - hang Ajeet Yadav
2011-04-27 17:11 ` Christoph Hellwig [this message]
2011-04-28  7:29   ` Ajeet Yadav
2011-05-02  5:41     ` Ajeet Yadav
2011-05-03 17:39       ` 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=20110427171107.GA29196@infradead.org \
    --to=hch@infradead.org \
    --cc=ajeet.yadav.77@gmail.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