From: Dave Chinner <david@fromorbit.com>
To: Chandra Seetharaman <sekharan@us.ibm.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: xfs_force_shutdown() called when running xfstests on 2.6.38-rc4
Date: Fri, 18 Feb 2011 14:30:30 +1100 [thread overview]
Message-ID: <20110218033030.GL13052@dastard> (raw)
In-Reply-To: <1297994980.32230.309.camel@chandra-lucid.beaverton.ibm.com>
On Thu, Feb 17, 2011 at 06:09:40PM -0800, Chandra Seetharaman wrote:
> On Fri, 2011-02-18 at 09:52 +1100, Dave Chinner wrote:
> > On Thu, Feb 17, 2011 at 10:49:10AM -0800, Chandra Seetharaman wrote:
> > > Thanks for that info, Eric.
> > >
> > > Now I increased the filesystem size and I see the following failure
> > > --------------------------------
> > > QA output created by 180
> > > file /mnt/xfsScratchMntPt/456 has incorrect size - sync failed
> > > file /mnt/xfsScratchMntPt/525 has incorrect size - sync failed
> > > file /mnt/xfsScratchMntPt/624 has incorrect size - sync failed
> > > ---------------------------------
> > >
> > > I guess that is not good :)
> >
> > No, not good. It passes here on x86_64 and a couple of different
> > configurations storage back ends (1/2p on h/w raid1 writing
> > @~90MB/s, 8p + s/w RAID0 @ ~700MB/s), so it doesn't seem like there
> > is a generic problem.
> >
> > what is the hardware you are testing on?
> PPC64
Yes, I know you are running on PPC64, but that doesn't tell me
anything about the hardware you are running on. How many CPUs, how
much RAM, what storage you are using, how it is configured, etc, is
the sort of infomration relevant to understanding the circumstances
around the failures you are seeing...
> > Does it happen on every run?
>
> No, it is not consistent. It happened as this
>
> +file /mnt/xfsScratchMntPt/993 has incorrect size - sync failed
>
> and ran 10+ times, didn't fail at all.
OK. So it's a relatively rare failure, then?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-02-18 3:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 19:41 xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 Chandra Seetharaman
2011-02-15 22:30 ` Dave Chinner
2011-02-16 20:00 ` Chandra Seetharaman
2011-02-16 22:14 ` Dave Chinner
2011-02-16 22:53 ` [PATCH] xfstests: Notify via syslog when godown is shutting down fs Eric Sandeen
2011-02-17 17:33 ` Chandra Seetharaman
2011-02-21 23:30 ` Alex Elder
2011-02-16 23:42 ` xfs_force_shutdown() called when running xfstests on 2.6.38-rc4 Chandra Seetharaman
2011-02-17 3:00 ` Eric Sandeen
2011-02-17 18:49 ` Chandra Seetharaman
2011-02-17 22:52 ` Dave Chinner
2011-02-18 2:09 ` Chandra Seetharaman
2011-02-18 3:30 ` Dave Chinner [this message]
2011-02-18 19:57 ` Chandra Seetharaman
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=20110218033030.GL13052@dastard \
--to=david@fromorbit.com \
--cc=sandeen@sandeen.net \
--cc=sekharan@us.ibm.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