Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Nov 2004 19:04:21 +0000
From:      Robin Breathe <robin+spam@isometry.net>
To:        Pawel Jakub Dawidek <pjd@FreeBSD.org>, freebsd-geom@FreeBSD.org
Cc:        Terje Elde <terje+geom@elde.net>
Subject:   Re: gmirror problems
Message-ID:  <41950935.2010103@isometry.net>
In-Reply-To: <20041108164540.GF8120@darkness.comp.waw.pl>
References:  <200411081140.57792.michael.riexinger@de.clara.net> <20041108120513.GH11057@calleigh.elde.net> <20041108124606.GC8120@darkness.comp.waw.pl> <200411081540.05593.michael.riexinger@de.clara.net> <20041108164540.GF8120@darkness.comp.waw.pl>

next in thread | previous in thread | raw e-mail | index | archive | help
Pawel Jakub Dawidek wrote:
> Unfortunately, gmirror and other GEOM classes are not supported by our
> installer.
> 
> The safest way to do what you want is to:
> 
> 	# gmirror label <name> ad1
> 	create slices and partitions on /dev/mirror/<name>
> 	create file system
> 	copy data from ad0 to <name>
> 	change /etc/fstab to boot from /dev/mirror/<name>s1a or something
> 	reboot
> 	# gmirror insert <name> ad0

Are any nasty side-effects likely from slicing and newfs-ing ad1 prior 
to labelling the mirror? For example, could the gmirror metadata get 
overwritten at some later stage by writing to the end of the last slice?

Robin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41950935.2010103>