Jeff Garzik wrote:
[linux I/O layer loops forever on SATA drive unplug;
SATA hotplug is unsupported yet]
It isn't hotPLUG -- it's hotUNplug. Happens when drive is dying for
Same difference to me: both require new code.
Jeff,
I didn't want to blame you or anyone else (just in case
if that wasn't clear). Instead, I just wanted to understand
what's the current state of the whole thing. I know SATA
hotplug is unsupported, and some code has to be written for
that to work. But I don't know if hotUNplugging and error
handling comes together. That is, is there a difference
between real drive failure (and oh, there are alot of various
failure scenarios too, from bad block, including a drive dying
completely during normal operations as if there wa no drive at
all, up to unplugging the cable by a mistake) and such hot-
UN-plugging? Will current code notice and properly propagate
I/O errors on the drive, or drive dying? If some errors are
propagated properly now, Where's the "boundary" between I/O
errors (implemented) and hotplug (not implemented)?
This all is quite important IMHO. Without proper error handling
(if I/O errors are "blacked" by that "boundary" too), linux SATA
subsystem isn't ready for production, and people should not
rely on it *now*.
/mjt
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
