Mark Lord wrote:Jeff Garzik wrote:Paolo Ornati wrote:Yeah, that's pretty suspicious. Prior to issuing a FLUSH_CACHE op,I have this problem only with XFS, and even with XFS it goes awayThis last is an interesting datapoint.
mounting with "nobarrier"...
I wonder if libata has a generic problem with NCQ + FLUSH CACHE.
one must first drain all outstanding NCQ commands (and not issue new ones).
I'm sure the code must *try* to do that, but perhaps there's a bug in
Or just another drive bug?
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 Seagate drive showing this problem.