LKML Archive on
help / color / mirror / Atom feed
From: "Phillip O'Donnell" <>
To: "Ric Wheeler" <>
Cc: "Alan Cox" <>,
	"Oskar Liljeblad" <>,
	"Robert Hancock" <>,
Subject: Re: sata errors with Seagate 1.5TB on AMD 780G/SB700 motherboard
Date: Thu, 30 Oct 2008 09:52:04 +1300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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?


> 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).

  reply	other threads:[~2008-10-29 20:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
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 [this message]
2008-10-29 22:37           ` Ric Wheeler
2008-11-07 11:33             ` Kasper Sandberg
2008-11-07 12:27               ` Ric Wheeler
     [not found] ` <>
     [not found]   ` <>
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).