>>>>> "Jeremy" == Jeremy Linton <jlinton@xxxxxxxxxxxxx> writes: >> others. We see cases fairly often where a misbehaving target has >> confused the HBA enough that we can not bring the device back without >> doing an HBA firmware reset. Despite I/O completing successfully on >> other targets connected to the same HBA. Jeremy> This would seem to indicate a HBA/driver bug... Yep. It's not just targets that go bad! Jeremy> Except that I've seen the linux error recovery cause more Jeremy> problems than it solves on a fairly regular basis. I would Jeremy> rather have a solution designed to isolate failures, than one Jeremy> that makes a lot of mistakes and causes further problems Jeremy> (sometimes with other machines). I'm pretty convinced that Jeremy> attempting everything possible to recover a device when the Jeremy> underlying problem is unknown is a bad strategy. There is no one size that fits all. Which is why we're taking steps to make the error recovery parameters tweakable. -- Martin K. Petersen Oracle Linux Engineering -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
