linux-kernel - Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46FFC42A.9080300@garzik.org>
Date:	Sun, 30 Sep 2007 11:43:38 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Paolo Ornati <ornati@...twebnet.it>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>, Tejun Heo <htejun@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-ide@...r.kernel.org
Subject: Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS

Paolo Ornati wrote:
> On Sun, 30 Sep 2007 11:05:17 -0400
> Jeff Garzik <jeff@...zik.org> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/