Messages in this thread | | | Subject | Re: [RFD] What error should FS return when I/O failure occurs? | From | fs <> | Date | Tue, 17 May 2005 11:43:00 -0400 |
| |
On Mon, 2005-05-16 at 11:42, Chris Siebenmann wrote: > You write: > | When I/O failure occurs, there should be some standards which > | define the ONLY error that should be returned from VFS, right? > > In practice there is no standard and there never will be any standard. > In general the only thing code can do on any write error is to abort > the operation, regardless of what errno is. (The exceptions are for > things like nonblocking IO, where 'EAGAIN' and 'EWOULDBLOCK' are not > real errors.) Yes, we're sure to abort the operation, but we can't use exit(EXIT_FAILURE) directly. For HA environment, we should identify the cause of the error, take correspondent action, right? So we need to get the right error. > --- > "I shall clasp my hands together and bow to the corners of the world." > Number Ten Ox, "Bridge of Birds" > cks@utcc.toronto.edu utgpu!cks
regards, ---- Qu Fuping
- 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/
| |