Re: writing file to disk: not as easy as it looks

[Mikulas Patocka]

On Wed, 3 Dec 2008, Pavel Machek wrote:

> > > CRC errors, lost IRQs and the like are retried by the midlayer and
> > > drivers and the error handling strategies will also try things like
> > > reducing link speeds on repeated CRC errors.
> > 
> > I meant for example loose cable or so --- does it make sense to retry 
> > indefinitely (until the admin plugs the cable or unmounts the filesystem) 
> > or return error to the filesystem after few retries?
> 
> It is quite non-trivial to detect if it is "disk plugged back in"
> vs. "faulty disk unplugged, new one plugged in"... so I suppose
> automatic retry after failure of connection to disk is quite hard to
> get right.

Unless the SATA controller has the plug interrupt (very few have), there 
is no way for the kernel to detect that an old SATA disk was unplugged and 
a new one was plugged in.

So the answer is that the admin must not hot-swap disk unless unmounting 
the filesystem or notifying the RAID layer about it. If you hot-swap 
softraid1/4/5 disk, you definitely damage data, because the softraid layer 
has no way to find out about the hotswap.

Mikulas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/