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 --- [EMAIL PROTECTED] *** ------------------------------------------------------------------------ _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[EMAIL PROTECTED]"
