Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS

Paolo Ornati wrote:
On Sun, 30 Sep 2007 11:05:17 -0400
Jeff Garzik <jeff@xxxxxxxxxx> 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.

What happens if you enable the 'fua' module parameter? (libata.fua on kernel command line, if built in)

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?

That message is normal, because libata defaults to FUA==off.

Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: Playing with SATA NCQ
    ... request as is currently done with NCQ commands. ... add an internal libata qc queue for postponing these commands. ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: Status of NCQ in libata
    ... I'd like to know about the current status of NCQ support in libata, ... Only one real bit needs to get merged in libata for ncq to be submitted, ...
    (Linux-Kernel)