Messages in this thread | | | Date | Sun, 30 Sep 2007 11:43:38 -0400 | From | Jeff Garzik <> | Subject | Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS |
| |
Paolo Ornati wrote: > On Sun, 30 Sep 2007 11:05:17 -0400 > Jeff Garzik <jeff@garzik.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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |