Date: Thu, 12 Apr 2012 10:58:01 +0200 From: Peter Maloney <peter.maloney@brockmann-consult.de> To: freebsd-fs@freebsd.org Subject: Re: zfs & gmirror == DIRTY mirror on reboot Message-ID: <4F869919.9060802@brockmann-consult.de> In-Reply-To: <20120412084006.GA32749@zxy.spb.ru> References: <20120411141243.GR32749@zxy.spb.ru> <CALfReyddp%2BEcObi-nW8_YSXRCVcU_BCAnCp=Y8fqm0680hA_ug@mail.gmail.com> <20120412084006.GA32749@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/12/2012 10:40 AM, Slawa Olhovchenkov wrote: > On Thu, Apr 12, 2012 at 09:34:47AM +0100, krad wrote: > >> On 11 April 2012 15:12, Slawa Olhovchenkov<slw@zxy.spb.ru> wrote: >>> Can some one fixing kern/113957#replay4? >>> Creating ZFS over gmirror causing gmirror DIRTY on correct reboot. >> this seams like a bizarre configuration. Why not let zfs do the >> mirroring as its more efficient in many ways? > I am need to reliable boot (toleranted to bad blocks in boot area, boot1/boot2). > reliable boot => mirror in bios. > PREC S100 don't have on-disk information about mirror => gmirror on OS > level. What's wrong with mirroring your / and /boot with zfs, and then if the bootcode blocks get broken, just do the bootcode commands again: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da1 gmirroring your bootcode won't do anything more than this would, since it is static content. (Or are you not talking about bootcode?) > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F869919.9060802>