From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: XFS mounting fails on MIPS
Date: Thu, 04 Nov 2010 05:23:23 -0500 [thread overview]
Message-ID: <4CD2899B.5040101@hardwarefreak.com> (raw)
In-Reply-To: <AANLkTi=mLwQ0N_cErHzES1ZWvOa8jQspeYwKgn9sU4Jm@mail.gmail.com>
Ajeet Yadav put forth on 11/4/2010 12:57 AM:
> Filesystem "sda2": Corruption of in-memory data detected.
That would lead me to believe you have a hardware problem. Could be a
bad DIMM, a bad board, defective PSU with too much voltage swing, etc,
etc. I'd start by replacing the DIMM(s) and go from there with process
of elimination.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-11-04 10:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 5:57 XFS mounting fails on MIPS Ajeet Yadav
2010-11-04 10:23 ` Stan Hoeppner [this message]
2010-11-04 12:40 ` Dave Chinner
2010-11-04 12:50 ` Christoph Hellwig
2010-11-09 11:13 ` Ajeet Yadav
2010-11-09 14:05 ` Christoph Hellwig
2010-11-11 4:57 ` Ajeet Yadav
2010-11-11 5:40 ` Ajeet Yadav
2010-11-11 12:49 ` Christoph Hellwig
2010-11-11 14:56 ` Ajeet Yadav
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=4CD2899B.5040101@hardwarefreak.com \
--to=stan@hardwarefreak.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