Recently I have seen cases where I/O to a device with bad media
was never noticed (except in the syslog). I think that is bad.
The application writes, but the stuff written lives in buffers.
The close() still does not force file I/O.
But the umount() causes the I/O to happen. Writes fail and the
syslog is full of messages. But the user does not see any messages,
the umount returns without error, and there is no reason to suspect
that anything is wrong.
I am not sure about the correct solution.
Perhaps umount should return -EIO if it did the umount but
I/O errors happened?
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
