[ 102/110] rbd: fix I/O error propagation for reads

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Josh Durgin commit 17c1cc1d9293a568a00545469078e29555cc7f39 upstream. When a request returns an error, the driver needs to report the entire extent of the request as completed. Writes already

[ 109/117] rbd: fix I/O error propagation for reads

3.11-stable review patch. If anyone has any objections, please let me know. -- From: Josh Durgin commit 17c1cc1d9293a568a00545469078e29555cc7f39 upstream. When a request returns an error, the driver needs to report the entire extent of the request as completed. Writes already

Re: I/O error propagation

I agree. But what if the file systems can handle certain errors better than what the drivers can do now ? Take for e.g., data corruption. If the driver finds a corrupted sector that it cannot recover, it is going to convert this specific error in to a more generic error code (-EIO) and report it t

Re: I/O error propagation

On Thu, 3 Mar 2005, V P wrote: Hi, I have a question on how disk errors get propagated to the file systems. From looking at the SCSI/IDE drivers, it looks like there could be many reasons for an I/O to fail. It could be bus timeout, media errors, and so on. Does all these errors get reported to the

I/O error propagation

Hi, I have a question on how disk errors get propagated to the file systems. >From looking at the SCSI/IDE drivers, it looks like there could be many reasons for an I/O to fail. It could be bus timeout, media errors, and so on. Does all these errors get reported to the file system ? It looks lik