Am 22.12.2017 um 01:11 hat Jack Schwartz geschrieben:
> BLOCK_IO_ERROR events currently contain a "reason" string which is
> strerror(errno) of the error.  This enhancement provides those events with
> the numeric errno value as well, since it is easier to parse for error type
> than a string.
> 
> Signed-off-by: Jack Schwartz <jack.schwa...@oracle.com>
> Reviewed-by: Konrad Rzeszutek Wilk <konrad.w...@oracle.com>
> Reviewed-by: Karl Heubaum <karl.heub...@oracle.com>

Apart from the technical details that Eric mentioed, I wonder what is
your use case for this?

Exposing errors in a machine readable form was discussed earlier, and
the result was that nobody had an actual use for error codes other than
presenting the right error message to the user - which the error string
already achieves.

The only exception so far was ENOSPC, which some management tools like
oVirt respond to by increasing the volume size, so this was mapped into
a bool.

Kevin

Reply via email to