Date: Fri, 11 May 2012 12:08:53 +0100 From: Karl Pielorz <kpielorz_lst@tdx.co.uk> To: Alexander Motin <mav@FreeBSD.org>, freebsd-geom@FreeBSD.org Subject: Re: FreeBSD 9-R amd64 - graid, should it survive 'pulling' a disk? Message-ID: <61CDA17B687F1C733EE1B017@OctaHexa64-MkII> In-Reply-To: <4FABDE10.8090304@FreeBSD.org> References: <4FABDE10.8090304@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--On 10 May 2012 18:26 +0300 Alexander Motin <mav@FreeBSD.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?61CDA17B687F1C733EE1B017>