Date: Mon, 27 Apr 2009 06:37:36 -0700 (PDT) From: Peter Steele <psteele@maxiscale.com> To: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> Cc: #freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Unexpected gmirror behavior: Is this a bug? Message-ID: <2732371.101240839456548.JavaMail.HALO$@halo> In-Reply-To: <18933005.81240838051541.JavaMail.HALO$@halo>
next in thread | previous in thread | raw e-mail | index | archive | help
> i think it's a bug but only happens with such massive mirror. very few >people do more than 2-way mirrors that's probably it wasn't catched. > >please do report the bug - it's critical. In fact I just confirmed that if we reduce our mirror to just two members the problem does not occur. The returning member, even if it is the first drive, is always re-synced with the data from the other drive and no data is lost. And yes, it's definitely a critical bug. I'm filing a bug report now, but we may have to fix this in-house before we can release our product with this problem. There is too great a risk for customers to lose data. Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2732371.101240839456548.JavaMail.HALO$>