All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Engel <david@istwok.net>
To: Michael-John Turner <mj@mjturner.net>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: XFS/driver bug or bad drive?
Date: Wed, 7 Oct 2009 10:20:11 -0500	[thread overview]
Message-ID: <20091007152011.GA19915@opus.istwok.net> (raw)
In-Reply-To: <20091007140431.GB29528@aurora.pimp.org.za>

On Wed, Oct 07, 2009 at 03:04:31PM +0100, Michael-John Turner wrote:
> On Wed, Oct 07, 2009 at 08:24:41AM -0500, Eric Sandeen wrote:
> > Firmware bug?  I still think it can't be an xfs problem, and I'm not
> > just trying to be protective of our turf ;)
> 
> Could very well be a firmware bug - FWIW, my drive has version 1AA01109.

A firmware bug wouldn't surprise me.  FWIW, here are my firmware
versions and latest information.

The problematic drive has firmware version 1AA01110.  I don't trust
that specific drive, don't really trust that model anymore, so I
retired it and bought a new drive to replace it.

The other HD753LJ I have (also replacement) has firmware version
1AA01110 too.  This drive hasn't shown any problems yet, but I will be
testing it more after I finish moving some files around.

> Some searching online suggests that others have solved similar problems by
> replacing their SATA cables. I'll give that a try but, as my issue isn't
> reproducible (subsequent cvs updates haven't given any problems), it'll be
> difficult to know immediately if a faulty cable was the problem.

I probably ran across all of the same stuff.  I tried multiple cables,
multiple SATA ports and multiple host systems.  The problem was nearly
100% on the intended system.  I don't know how frequent the problem
was on the second system since I stopped testing on it after the first
failure confirmed the problem was not specific to the original system.

David
-- 
David Engel
david@istwok.net

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

  reply	other threads:[~2009-10-07 15:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01 23:27 XFS/driver bug or bad drive? David Engel
2009-10-02  0:39 ` Eric Sandeen
2009-10-02 16:57   ` David Engel
2009-10-07 11:29     ` Michael-John Turner
2009-10-07 13:24       ` Eric Sandeen
2009-10-07 14:04         ` Michael-John Turner
2009-10-07 15:20           ` David Engel [this message]
2009-10-02  8:05 ` Michael Monnerie

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=20091007152011.GA19915@opus.istwok.net \
    --to=david@istwok.net \
    --cc=mj@mjturner.net \
    --cc=sandeen@sandeen.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.