From: Ric Wheeler <rwheeler@redhat.com>
To: "Phillip O'Donnell" <phillip.odonnell@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Oskar Liljeblad <oskar@osk.mine.nu>,
Robert Hancock <hancockr@shaw.ca>,
linux-kernel@vger.kernel.org
Subject: Re: sata errors with Seagate 1.5TB on AMD 780G/SB700 motherboard
Date: Wed, 29 Oct 2008 18:37:42 -0400 [thread overview]
Message-ID: <4908E5B6.1080703@redhat.com> (raw)
In-Reply-To: <7a9b5c320810291352k5db86a4eg4e03fb09317de459@mail.gmail.com>
Phillip O'Donnell wrote:
> Hi Ric,
>
> Not too sure about that - I run with XFS, which announces that it
> disables the barriers on my devices (I use LVM on top of them) but
> still get the same issue... Unless I've misunderstood your comment?
>
> Cheers,
> Phillip
>
XFS has a different issue with barriers that has been recently fixed.
I am just going based on what I read at the Seagate customer site - it
looks like the hang was during the processing of the ATA_CACHE_FLUSH_EXT
command.
New drives are routinely buggy to some degree, especially ones that jump
up in capacity :-) Seagate has a well earned reputation for quality and
I will be surprised if they don't fix this issue soon,
Ric
>
>> I suspect that the drive is simply choking on the barrier related cache
>> flushing that we do - that seemed to be the MacOS error as well. The windows
>> comment suggested that windows had an hba/driver bug (most likely unrelated
>> to this).
>>
>> If you want to avoid the issue until they fix the drive, you could run fast
>> and dangerous (mount without barriers on) or slow and safe (disable the
>> write cache).
>>
next prev parent reply other threads:[~2008-10-29 22:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.01zEaARwrup2dCOTuHTYxzuS9BI@ifi.uio.no>
2008-10-28 23:19 ` sata errors with Seagate 1.5TB on AMD 780G/SB700 motherboard Robert Hancock
2008-10-29 18:58 ` Oskar Liljeblad
2008-10-29 20:17 ` Alan Cox
2008-10-29 20:23 ` Ric Wheeler
2008-10-29 20:52 ` Phillip O'Donnell
2008-10-29 22:37 ` Ric Wheeler [this message]
2008-11-07 11:33 ` Kasper Sandberg
2008-11-07 12:27 ` Ric Wheeler
[not found] ` <fa.Dwk+NgWNu7+JRcsgOPCxSr7y5SQ@ifi.uio.no>
[not found] ` <fa.fIxdVik0iPc+lS+sd5ef+ZoALzQ@ifi.uio.no>
2008-10-30 0:39 ` [PATCH] libata: Avoid overflow in ata_tf_to_lba48() when tf->hba_lbal > 127 Robert Hancock
2008-10-28 17:01 sata errors with Seagate 1.5TB on AMD 780G/SB700 motherboard Oskar Liljeblad
2008-10-28 17:59 ` David Rees
2008-10-28 23:25 ` Phillip O'Donnell
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=4908E5B6.1080703@redhat.com \
--to=rwheeler@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=oskar@osk.mine.nu \
--cc=phillip.odonnell@gmail.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