On Tue, 02 Oct 2007 18:19:14 +0900
Tejun Heo <[EMAIL PROTECTED]> wrote:
> Yeah, "World's first" is a pretty good clue indicating "broken".
> Blacklisting it seems like a good idea after all.
OT: I cannot test anything NCQ related for a while because the Intel
Mobo departed yesterday, so I'm on a
Hello,
Mark Lord wrote:
> Mmm.. $66 for "open box". But the drive itself has been discontinued by
> Seagate,
Couldn't find any in SUSE and I don't think I can't find any vendor who
still carries the drive here.
> and once claimed to be "World's first SATA desktop drive with NCQ.".
>
> Probably
On 10/01/2007 01:45 AM, Robert Hancock wrote:
> Are you sure this isn't just a bum drive? Looking at the SMART listing
> that was posted, looks like it's had some uncorrectable sector read
> errors in the event log..
Seagate is known to report wrong numbers in smart.
regards,
--
Jiri Slaby ([EMA
On Sun, 30 Sep 2007 17:45:41 -0600
Robert Hancock <[EMAIL PROTECTED]> wrote:
> Are you sure this isn't just a bum drive? Looking at the SMART listing
> that was posted, looks like it's had some uncorrectable sector read
> errors in the event log..
Don't know. The error count is still 12 today,
Paolo Ornati wrote:
Hi, I think you forgot to blacklist this one :)
--
Seagate Barracuda ST380817AS has troubles with NCQ. For example,
unpacking a tarball on an XFS filesystem gives this:
ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
ata1.00: cmd 61/40:00:29:a3:98/00:00:00:
Mark Lord wrote:
Tejun Heo wrote:
Mark Lord wrote:
Tejun Heo wrote:
Mark Lord wrote:
If there was such a bug, the aborted commands list should contain both
FPDMA commands and FLUSH commands. I don't think command filtering
itself is broken. Possibly another quirky firmware but it's strange
t
Tejun Heo wrote:
Mark Lord wrote:
Tejun Heo wrote:
Mark Lord wrote:
If there was such a bug, the aborted commands list should contain both
FPDMA commands and FLUSH commands. I don't think command filtering
itself is broken. Possibly another quirky firmware but it's strange
that this is the on
Mark Lord wrote:
> Tejun Heo wrote:
>> Mark Lord wrote:
>> If there was such a bug, the aborted commands list should contain both
>> FPDMA commands and FLUSH commands. I don't think command filtering
>> itself is broken. Possibly another quirky firmware but it's strange
>> that this is the only S
Tejun Heo wrote:
Mark Lord wrote:
Jeff Garzik wrote:
Paolo Ornati wrote:
I have this problem only with XFS, and even with XFS it goes away
mounting with "nobarrier"...
This last is an interesting datapoint.
I wonder if libata has a generic problem with NCQ + FLUSH CACHE.
Yeah, that's pretty
Mark Lord wrote:
> Jeff Garzik wrote:
>> Paolo Ornati wrote:
>>> I have this problem only with XFS, and even with XFS it goes away
>>> mounting with "nobarrier"...
>>
>> This last is an interesting datapoint.
>>
>> I wonder if libata has a generic problem with NCQ + FLUSH CACHE.
>
> Yeah, that's p
Jeff Garzik wrote:
Paolo Ornati wrote:
On Sun, 30 Sep 2007 15:29:08 +0100
Alan Cox <[EMAIL PROTECTED]> wrote:
Seagate Barracuda ST380817AS has troubles with NCQ. For example,
unpacking a tarball on an XFS filesystem gives this:
ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
On Sun, 30 Sep 2007 11:59:45 -0400
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Is libata built into the kernel, or a module?
built-in, my kernel is pretty monolithic
--
Paolo Ornati
Linux 2.6.23-rc8-ga64314e6 on x86_64
-
To unsubscribe from this list: send the line "unsubscribe lin
Paolo Ornati wrote:
On Sun, 30 Sep 2007 11:43:38 -0400
Jeff Garzik <[EMAIL PROTECTED]> wrote:
it isn't supported here:
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Did you actually try my suggestion?
Yes ("libata.fua=1" is ok I think, or it should
On Sun, 30 Sep 2007 11:43:38 -0400
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> > it isn't supported here:
> > sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
> > support DPO or FUA
>
> Did you actually try my suggestion?
Yes ("libata.fua=1" is ok I think, or it should just b
Paolo Ornati wrote:
On Sun, 30 Sep 2007 11:05:17 -0400
Jeff Garzik <[EMAIL PROTECTED]> wrote:
I have this problem only with XFS, and even with XFS it goes away
mounting with "nobarrier"...
This last is an interesting datapoint.
I wonder if libata has a generic problem with NCQ + FLUSH CACHE
On Sun, 30 Sep 2007 11:05:17 -0400
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> > I have this problem only with XFS, and even with XFS it goes away
> > mounting with "nobarrier"...
>
> This last is an interesting datapoint.
>
> I wonder if libata has a generic problem with NCQ + FLUSH CACHE.
>
>
Paolo Ornati wrote:
On Sun, 30 Sep 2007 15:29:08 +0100
Alan Cox <[EMAIL PROTECTED]> wrote:
Seagate Barracuda ST380817AS has troubles with NCQ. For example,
unpacking a tarball on an XFS filesystem gives this:
ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
ata1.00: cmd 61/40:0
On Sun, 30 Sep 2007 15:29:08 +0100
Alan Cox <[EMAIL PROTECTED]> wrote:
> > Seagate Barracuda ST380817AS has troubles with NCQ. For example,
> > unpacking a tarball on an XFS filesystem gives this:
> >
> > ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
> > ata1.00: cmd 61/40:00:2
On Sun, 30 Sep 2007 07:17:05 -0700
Tejun Heo <[EMAIL PROTECTED]> wrote:
> Paolo Ornati wrote:
> > Seagate Barracuda ST380817AS has troubles with NCQ. For example,
> > unpacking a tarball on an XFS filesystem gives this:
> >
> > ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
> >
On Sun, 30 Sep 2007 16:05:48 +0200
Paolo Ornati <[EMAIL PROTECTED]> wrote:
> Hi, I think you forgot to blacklist this one :)
>
> --
> Seagate Barracuda ST380817AS has troubles with NCQ. For example,
> unpacking a tarball on an XFS filesystem gives this:
>
> ata1.00: exception Emask 0x0 SAct 0x1
Paolo Ornati wrote:
> Seagate Barracuda ST380817AS has troubles with NCQ. For example,
> unpacking a tarball on an XFS filesystem gives this:
>
> ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
> ata1.00: cmd 61/40:00:29:a3:98/00:00:00:00:00/40 tag 0 cdb 0x0 data 32768 out
>
21 matches
Mail list logo
