s...@stix.id.au (Paul Ripke) writes:
>I guess I'm a little surprised by this error?
>Nor does read(2) list EROFS as a possible return, which seems sensible.
The errors listed with system calls are rarely complete, in particular for
errors you rarely observe or here for operations on something
So I have a dying disk (WD20EARX) in a USB enclosure, and I tried to
do some random reads against the raw device:
read I/O failed, offset 363065167872: 30 (Read-only file system)
I guess I'm a little surprised by this error?
Nor does read(2) list EROFS as a possible return, which seems sensible.
