From owner-freebsd-current@FreeBSD.ORG Mon Oct 11 13:26:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE31916A4CE for ; Mon, 11 Oct 2004 13:26:13 +0000 (GMT) Received: from clueful.shagged.org (clueful.shagged.org [212.13.201.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66AF243D54 for ; Mon, 11 Oct 2004 13:26:13 +0000 (GMT) (envelope-from chris@clueful.shagged.org) Received: from chris by clueful.shagged.org with local (Exim 4.40 (FreeBSD)) id 1CH0Bi-000MTm-O6; Mon, 11 Oct 2004 14:26:06 +0100 Date: Mon, 11 Oct 2004 14:26:06 +0100 From: Chris Elsworth To: Christian Hiris <4711@chello.at> Message-ID: <20041011132606.GA86235@shagged.org> References: <20041010110159.GA91160@pcs28.suedfactoring.de> <200410101522.45548.4711@chello.at> <20041010165852.GA15854@shagged.org> <200410110026.03777.4711@chello.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200410110026.03777.4711@chello.at> User-Agent: Mutt/1.5.6i Sender: Chris Elsworth X-Shagged-MailScanner-Information: See www.mailscanner.info for information X-Shagged-MailScanner: Found to be clean X-MailScanner-From: chris@clueful.shagged.org cc: axel.gruner@suedfactoring.de cc: freebsd-current@freebsd.org Subject: Re: RAID1 with gmirror X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2004 13:26:13 -0000 On Mon, Oct 11, 2004 at 12:25:46AM +0200, Christian Hiris wrote: > > > 4) bsdlabel -e ad0 [taking into account the new 16 byte offset] > > I never read about the new offset - until now I had no time to study the > gmirror code. Where did you find this interresting information? Here (and related thread): http://lists.freebsd.org/pipermail/freebsd-geom/2004-September/000313.html > An example in 'man gmirror' describes how to set up a gmirror array on a disk > with valid data. It uses 'gmirror lable' w/o extra labeling. I understand it > the way that the term 'valid data' means 'existing (non-gmirror-)data on an > already (before-gmirror-)labeled disk'. Maybe my understanding is wrong and > you gave me the hint to the reason why my mirrors break on startup. I will do > some testing on this. No, I get the mirrors breaking on startup too. I believe this is fixed in -CURRENT but is pending a MFC into RELENG_5 to fix. So, I'm left quite unsure whether the warnings are harmless or not. Pawel, can we just use existing labels on disks and apply a gmirror over it, or should we be re-labelling inside the mirror device? -- Chris