Harshavardhana fc5213258e
posix: Do not take disk offline on I/O errors (#8836)
Choosing maxAllowedIOError is arbitrary and
prone to errors, when drives might be perfectly
capable of taking I/O with only few locations
return I/O error. This is a hindrance of sort
where backend filesystems like ZFS can automatically
fix and handle these scenarios.

The added problem with current approach that we
take the drive offline, making it virtually impossible
to bring it online without restart the server which
is not desirable on a busy cluster. Remove this state
such that let the backend return error appropriately
to caller and let the caller decide what to do with
the error.
2020-01-17 13:34:43 -08:00
..
2019-12-12 10:01:15 -08:00
2020-01-13 13:09:10 -08:00
2020-01-08 17:21:58 -08:00
2020-01-02 20:18:32 +05:30
2019-09-10 04:42:29 +05:30
2020-01-15 18:30:32 -08:00