Date: Fri, 24 Apr 2009 23:29:45 +0200 From: Ivan Voras <ivoras@freebsd.org> To: Peter Steele <psteele@maxiscale.com> Cc: freebsd-questions@freebsd.org Subject: Re: Unexpected gmirror behavior: Is this a bug? Message-ID: <9bbcef730904241429h70794144g14c9818e8189f7d9@mail.gmail.com> In-Reply-To: <29655217.2961240606345404.JavaMail.HALO$@halo> References: <gst6gn$b05$1@ger.gmane.org> <29655217.2961240606345404.JavaMail.HALO$@halo>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/4/24 Peter Steele <psteele@maxiscale.com>: >> This definitely looks like a bug. Try asking again on the freebsd-geom@ >> list. Provide output of "gmirror list". > > I'll try that list... > >>So, your steps were: > >>1. ad4, ad6, ad8 and ad10 in a 4-way mirror >>2. ad4 fails. At this point did you do a "gmirror list"? I.e. did >>gmirror detect it failing? If I read it correctly, the GenID field >>should have been increased in this case. >>3. The system continues to be used >>4. You power it down, take out and reinsert ad4 >>5. On boot, ad4 is detected, inserted in the mirror but as a "known >>good" copy, not a stale one. >> >>Correct? > > Yes, that's basically the sequence that occurred. I can easily recreate the > condition though. I shut my box down, took out ad4 and then rebooted. The > system complained about ad4 being missing and proceeded with a mirror using > 3/4 of the drives. I then created a file on the system, shutdown again, and > then reinserted ad4. On reboot as the system was starting up the gmirror > driver, it detected ad4 but instead of reinserting in in the most recent > mirror made up of the other drives, it became the active drive and kicked > out its old partners, By "kicked out" you mean "overwritten"? You should definitely look at "gmirror list" before and after.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9bbcef730904241429h70794144g14c9818e8189f7d9>