From: David Engel <david@istwok.net>
To: xfs@oss.sgi.com, Eric Sandeen <sandeen@sandeen.net>
Subject: Re: XFS/driver bug or bad drive?
Date: Fri, 2 Oct 2009 11:57:04 -0500 [thread overview]
Message-ID: <20091002165704.GA17558@opus.istwok.net> (raw)
In-Reply-To: <4AC54BDA.20806@sandeen.net>
On Thu, Oct 01, 2009 at 07:39:54PM -0500, Eric Sandeen wrote:
> These are all storage errors, not xfs. I suppose it could be
> differing IO patterns from one fs or the other that trips it up, but
> nothing above is related to an xfs bug; any xfs problems are in
> response to the above IO errors, maybe a hardware problem or a
> driver problem, not sure - but most likely a hardware issue I think.
> You might point smartctl at the drive and see what it says.
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.
Michael Monnerie wrote:
> Yes, that Samsung crap. Of the very few drives we had (the 1TB version),
> all got broken quickly, and we replaced them with Hitachis. It's a pity,
> as they had a nice price, but when they it your data, it's priceless.
I've used mostly Samsung drives for several years. This particular
750GB model is the only one that I consider a lemon.
David
--
David Engel
david@istwok.net
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-10-02 16:55 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 [this message]
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
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=20091002165704.GA17558@opus.istwok.net \
--to=david@istwok.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox