On Mon, Aug 6, 2012 at 9:26 AM, Maksim Yevmenkin <maksim.yevmen...@gmail.com> wrote: > On Mon, Aug 6, 2012 at 9:23 AM, Garrett Cooper <yaneg...@gmail.com> wrote: >> On Mon, Aug 6, 2012 at 8:34 AM, Maksim Yevmenkin >> <maksim.yevmen...@gmail.com> wrote: >>> Michael, >>> >>>> Something in -current and recently MFC'd to -stable is causing all of my >>>> gmirror drives to rebuild on reboot :-( >>>> >>>> Being remote and these being production machines, I suspect SVN r237929 >>>> and r237930 in -current and SVN r238500 to -stable but haven't yet been >>>> able to prove it. >>>> >>>> Is anyone else seeing this? >>> >>> yes, i've seem something similar only much, much worse. one of our >>> production systems completely kept loosing its gmirror volumes on >>> every reboot. it looked like gmirror metadata were completely >>> corrupted. rebuilding mirrors and reverting back to previous kernel >>> seemed to work. someone else is tracking it down. >> >> Is this is in 9.1 -PRERELEASE, -RELEASE (or whatever the official >> label is...)? If so, it seems like this would be a ship blocker. > > sorry. its releng_9/9-stable. gmirrors are on two ssds. we use gpt and > gmirror individual partitions, not entire disks.
I may well be confused, but I don't understand how you can use GPT for a single partition. Looks to me like a disk is GPT or legacy. Declaring which is the first command when setting up a new disk. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
