Stephen Satchell wrote:
>
> It is the responsibility of the power monitor to detect a power-fail
> event and tell the drive(s) that a power-fail event is occurring. If
> power goes out of specification before the drive completes a commanded
> write, what do you expect the poor drive to do? ANY glitch in the write
> current will corrupt the current block no matter what -- the final CRC
> isn't recorded. Most drives do have a panic-stop mode when they detect
> voltage going out of range so as to minimize the damage caused by an
> out-of-specification power-down event, and more importantly use the
> energy in the spinning platter to get the heads moved to a safe place
> before the drive completely spins down. The panic-stop mode is EXACTLY
> like a Linux OOPS -- it's a catastrophic event that SHOULD NOT OCCUR.
>
There is no "power monitor" in a PC system (at least not that is visible
to the drive) -- if the drive needs it, it has to provide it itself.
It's definitely the responsibility of the drive to recover gracefully
from such an event, which means that it writes anything that it has
committed to the host to write; anything it hasn't gotten committed to
write (but has received) can be written or not written, but must not
cause a failure of the drive.
A drive is a PERSISTENT storage device, and as such has responsibilities
the other devices don't.
Anything else is brainless rationalization.
-hpa
-
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/
This archive was generated by hypermail 2b29 : Fri Nov 30 2001 - 21:00:17 EST