From: Shawn Usry <shawn@dolphinlogic.com>
To: xfs@oss.sgi.com
Subject: Re: Interesting possible XFS crash condition
Date: Wed, 20 Oct 2010 23:45:03 -0500 [thread overview]
Message-ID: <4CBFC54F.8030403@dolphinlogic.com> (raw)
In-Reply-To: <20101020232758.51ac507a@galadriel.home>
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!
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-10-21 4:44 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 [this message]
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=4CBFC54F.8030403@dolphinlogic.com \
--to=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