The "reset: no matching NCQ I/O found" issue appears to be related to the error recovery for bad blocks on the disk. In general it should be harmless, but I have looked into this. If there is someone out there who; 1) Is hitting this issue, and; 2) Is running recent Solaris Nevada bits (not Solaris 10) and; 3) Is willing to try out an experimental driver
I can provide a new binary (with which I've done some testing already) which would appear to deal with this issue and do better and quicker error recovery. Remember that the underlying problem still appears to be bad blocks on the disk, so until those blocks are re-written or mapped away there will still be slow response and error messages generated each and every time those blocks are read. Regards, Lida This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss