public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: Shawn Usry <shawn@dolphinlogic.com>
Cc: xfs@oss.sgi.com
Subject: Re: Interesting possible XFS crash condition
Date: Wed, 20 Oct 2010 23:27:58 +0200	[thread overview]
Message-ID: <20101020232758.51ac507a@galadriel.home> (raw)
In-Reply-To: <4CBF3C6C.2020803@dolphinlogic.com>

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.

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

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

  reply	other threads:[~2010-10-20 21:27 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 [this message]
2010-10-21  4:45       ` Shawn Usry
2010-10-21  6:06         ` Dave Chinner
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=20101020232758.51ac507a@galadriel.home \
    --to=eflorac@intellique.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