public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Jay Ashworth <jra@baylink.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS recovery resumes...
Date: Mon, 19 Aug 2013 01:47:16 -0500	[thread overview]
Message-ID: <5211BF74.9060605@hardwarefreak.com> (raw)
In-Reply-To: <6f8bb504-c786-4bc0-9327-ee58a40d99e2@email.android.com>

On 8/18/2013 10:55 PM, Jay Ashworth wrote:
> Still the same outage from 2 weeks ago, Stan; my script had nothing to do with breaking the FSs. Was a zorched power supply, almost certainly. 

Sorry I missed this in your first post Jay.

> [1278872.584543] XFS (sda1): Corruption of in-memory data detected.
> Shutting down filesystem

Joe appears to have hit the nail on the head WRT this being a hardware
problem.  This error confirms it.  It would appear that when the Antec
PSU went South it damaged a motherboard device, possibly a VRM, probably
a cap or two, or more.  Maybe damaged a DRAM cell or few that work fine
with memtest86+ but not with the access pattern generated by your XFS
workload.

I'd first try manually clocking the DIMMs down a bit, from 400 to 333,
or 333 to 266, whichever is called for.  IIRC that VIA Northbrige has
decoupled CPU and DRAM buses so you should be able to clock the DRAM
down without affecting CPU frequency.  If the problem persists, swap the
DIMMs if you have some on hand or can get them really cheap like $10 for
a pair.  If that doesn't fix it, this may be a viable inexpensive solution:

http://www.newegg.com/Product/Product.aspx?Item=N82E16813186215
http://www.newegg.com/Product/Product.aspx?Item=N82E16819103888
http://www.newegg.com/Product/Product.aspx?Item=N82E16820145252

$109 to replace your central electronics complex.  This is the least
expensive quality set of parts with good feature set I could come up
with at Newegg, to take the sting out of dropping cash on a forced
upgrade.  $15 more for the Foxconn AM3 board w/HDMI if you have a newer
TV or AV receiver.  If it all ships from the Memphis warehouse it should
reach St. Petersburg in a few days, a couple more if items ship from the
LA or Newark facilities.  I very rarely get anything from Newark, mostly
from Memphis, then and LA.

-- 
Stan

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

  reply	other threads:[~2013-08-19  6:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <29874428.3384.1376259762936.JavaMail.root@benjamin.baylink.com>
2013-08-11 22:36 ` XFS recovery resumes Jay Ashworth
2013-08-18 21:38   ` Jay Ashworth
2013-08-18 21:51     ` Joe Landman
2013-08-18 22:11       ` Jay Ashworth
2013-08-18 22:57         ` Joe Landman
2013-08-18 23:21           ` Jay Ashworth
2013-08-18 22:06     ` Stan Hoeppner
2013-08-19  3:55       ` Jay Ashworth
2013-08-19  6:47         ` Stan Hoeppner [this message]
2013-08-24 23:43           ` Jay Ashworth
2013-08-25  3:44             ` Stan Hoeppner
2013-08-25 15:29               ` Jay Ashworth
2013-08-25 17:45                 ` Stan Hoeppner
2013-08-25 20:27                   ` Jay Ashworth
2013-08-26  5:45                     ` Stan Hoeppner
2013-08-26 15:42                       ` Jay Ashworth
2013-08-24 23:48           ` Default mkfs parms for my DVR drive Jay Ashworth
2013-08-25  0:00             ` Joe Landman
2013-08-25  0:41               ` Jay Ashworth
2013-08-25  3:41                 ` Jay Ashworth
2013-08-22  9:16   ` XFS recovery resumes Stefan Ring
2013-08-27 23:59     ` Dave Chinner
2013-08-28  0:19       ` Jay Ashworth

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=5211BF74.9060605@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=jra@baylink.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