--On 10 May 2012 18:26 +0300 Alexander Motin <[email protected]> wrote:
Hi.
This panic is not in graid code, but it can be called a problem of the
graid's RAID1 implementation. If some disk returns _write_ failure, that
failure may now be reported to higher levels. Problem is that UFS SU code
panics on these errors in some cases. I'll try to look on it nearest time.
Hi,
So for clarity - what you're saying is if one of the servers drops a disk
from it's graid RAID1 array (for whatever reason) while writing, the error
could 'bubble up' and have the UFS code panic, because of it? (even though
the write would have completed on the other drive)?
Is the same true for reads?
-Karl
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-geom
To unsubscribe, send any mail to "[email protected]"
