Date: Thu, 9 Mar 2006 20:01:25 +0300 (MSK) From: Dmitry Morozovsky <marck@rinet.ru> To: Ruslan Ermilov <ru@freebsd.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, Pawel Jakub Dawidek <pjd@freebsd.org>, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/geom/mirror g_mirror.c Message-ID: <20060309195433.O69649@woozle.rinet.ru> In-Reply-To: <20060309091410.GO54826@ip.net.ua> References: <200603080827.k288RXLb076843@repoman.freebsd.org> <20060308125450.I68519@woozle.rinet.ru> <20060309091300.GN54826@ip.net.ua> <20060309091410.GO54826@ip.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 9 Mar 2006, Ruslan Ermilov wrote: RE> > YMMV of course, but at work we prefer to mirror slices not disks. RE> ^^^^^^^^^^^^^ RE> > This way it's much more flexible -- you can have mirrored root, RE> > unmirrored swap, stripped+mirrored data, etc. RE> > RE> Err, I meant "mirror partitions" of course. :-) So do I. Hence, in standard mirror situation I have /dev/mirror/m0a from ad4a+ad6a for root, /dev/mirror/m0b from ad4b+ad6b for swap etc. Troubles was with crashdumps, so earlier I'd reserve ad4d without file system to dump to. Now it should be a bit simplier. To pjd@: idea from wild space: if one have to replace faulted disk he could have serious performance problems with syncing more than one gmirror/graid3 at a time. Maybe introduce a mechanism to suspend one or more sync process(es) when other are in progress? Or even max concurrency sync level? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060309195433.O69649>