From: Dave Chinner <david@fromorbit.com>
To: Shawn Usry <shawn@dolphinlogic.com>
Cc: xfs@oss.sgi.com
Subject: Re: Interesting possible XFS crash condition
Date: Thu, 21 Oct 2010 17:06:05 +1100 [thread overview]
Message-ID: <20101021060605.GS32255@dastard> (raw)
In-Reply-To: <4CBFC54F.8030403@dolphinlogic.com>
On Wed, Oct 20, 2010 at 11:45:03PM -0500, Shawn Usry wrote:
>
> On 10/20/2010 4:27 PM, Emmanuel Florac wrote:
> >Le Wed, 20 Oct 2010 14:01:00 -0500 vous écriviez:
> >
> >>2. I did upgrade the firmware on the controller to a newer version
> >>AFTER the issue appeared, hoping this would resolve it. Same results.
> >>
> >>At this point I'm leaning toward faulty hardware somewhere.
> >Another possibility is a memory problem, possibly making the machine
> >crash under heavy load; if most RAM is used as filesystem caching, this
> >maybe may lead to apparently xfs related errors. You could try running
> >memtest86+ on the system for a couple of hours.
> >
> Great minds think alike :) Actually I have indeed already run a
> memtest86+ on the system which completed without a problem.
> Loading up read/writes on other single disks on the system also
> doesn't produce a problem. Just this one filesystem ;) It's a
> stumper!
Having some idea of the log messages generated by the crash - even
if it is screen shorts via hand-held camera - might help us narrow
down the cause.
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:[~2010-10-21 6:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 6:13 Interesting possible XFS crash condition Shawn Usry
2010-10-20 8:12 ` Michael Monnerie
2010-10-20 19:01 ` Shawn Usry
2010-10-20 21:27 ` Emmanuel Florac
2010-10-21 4:45 ` Shawn Usry
2010-10-21 6:06 ` Dave Chinner [this message]
2010-10-20 9:54 ` Emmanuel Florac
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=20101021060605.GS32255@dastard \
--to=david@fromorbit.com \
--cc=shawn@dolphinlogic.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