public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: xfs crash forensics
Date: Wed, 21 Apr 2010 11:11:43 -0500	[thread overview]
Message-ID: <4BCF23BF.8070305@hardwarefreak.com> (raw)
In-Reply-To: <20100421152751.24c833f2@harpe.intellique.com>

Emmanuel Florac put forth on 4/21/2010 8:27 AM:
> Le Wed, 21 Apr 2010 06:41:29 -0500
> Stan Hoeppner <stan@hardwarefreak.com> écrivait:
> 
>> Smells like a disk going bad.  What does SMART say about the disk
>> attached to port 11?
>>
> 
> surprisingly, absolutely nothing after the reboot. The disk just
> "cleaned up" all by itself. There are any registered alarms on the
> controller, too.

You need to dig for more information on drive scsi6.  The messages logged
appear to be saying that many sectors were replaced with spares and the
originals marked bad.  Additionally, there appears to have been a bus
timeout during the same time period.  This leads me to believe that drive is
faulty and should be replaced.  Use smartctl or other tools to grab the
SMART data from that drive.  I'm not sure exactly how to do so with drives
connected to a 3ware controller.  IIRC smartctl needs some extra switches
for 3ware cards.  Google is your friend here.

Please don't go on as if nothing happened and everything is fine now.  You
need to find out if that drive is indeed going bad, which appears, from
here, to be the case.

-- 
Stan


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

      reply	other threads:[~2010-04-21 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21 11:12 xfs crash forensics Emmanuel Florac
2010-04-21 11:41 ` Stan Hoeppner
2010-04-21 13:27   ` Emmanuel Florac
2010-04-21 16:11     ` Stan Hoeppner [this message]

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=4BCF23BF.8070305@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