From: Eric Sandeen <sandeen@sandeen.net>
To: Michael-John Turner <mj@mjturner.net>
Cc: David Engel <david@istwok.net>, xfs@oss.sgi.com
Subject: Re: XFS/driver bug or bad drive?
Date: Wed, 07 Oct 2009 08:24:41 -0500 [thread overview]
Message-ID: <4ACC9699.70900@sandeen.net> (raw)
In-Reply-To: <20091007112959.GA17132@aurora.pimp.org.za>
Michael-John Turner wrote:
> On Fri, Oct 02, 2009 at 11:57:04AM -0500, David Engel wrote:
>> I agree it shouldn't be an xfs bug. I thought it was strange, though,
>> that the problem only seemed to show up with xfs on 2.6.30.x. IO
>> pattern sensitivity wouldn't surprise me, but I wanted to check all my
>> bases before giving up on the drive.
>
> Rather curiously, I had exactly the same issue with the same model drive
> this past weekend. Debian-patched 2.6.26 kernel, however, though also with
> XFS (on top of md/LVM). Interestingly, there were no SMART errors and a
> full SMART test passed. The error was triggered by doing a cvs update on my
> working copy of the NetBSD source tree - not a large copy, but a
> disk-intensive activity.
>
> -mj
Firmware bug? I still think it can't be an xfs problem, and I'm not
just trying to be protective of our turf ;)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-10-07 13:23 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 [this message]
2009-10-07 14:04 ` Michael-John Turner
2009-10-07 15:20 ` David Engel
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=4ACC9699.70900@sandeen.net \
--to=sandeen@sandeen.net \
--cc=david@istwok.net \
--cc=mj@mjturner.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.