From owner-freebsd-geom@FreeBSD.ORG Fri Sep 24 16:06:25 2004 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8B8F16A4CF for ; Fri, 24 Sep 2004 16:06:25 +0000 (GMT) Received: from clueful.shagged.org (clueful.shagged.org [212.13.201.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A80E43D1F for ; Fri, 24 Sep 2004 16:06:25 +0000 (GMT) (envelope-from chris@clueful.shagged.org) Received: from chris by clueful.shagged.org with local (Exim 4.40 (FreeBSD)) id 1CAsaS-000KO5-U0 for freebsd-geom@FreeBSD.org; Fri, 24 Sep 2004 17:06:20 +0100 Date: Fri, 24 Sep 2004 17:06:20 +0100 From: Chris Elsworth To: freebsd-geom@FreeBSD.org Message-ID: <20040924160620.GA77997@shagged.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 Subject: WARNING: Expected rawoffset 0, found 63 ? X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2004 16:06:26 -0000 Hello, I'm having a play with gmirror, but I'm consistently running up against this problem: WARNING: Expected rawoffset 0, found 63 My chain of events is this: Start with a fresh disk, one slice covering the entire disk, no partitions yet: app1# disklabel -r da1s1 # /dev/da1s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 71119692 0 unused 0 0 # "raw" part, don't edit Set up a gmirror on it (this disk only at the moment, no other providers): app1# gmirror label -hv gms1 da1s1 Metadata value stored on da1s1. Done. In response to this command on console I see the following: GEOM_MIRROR: Device gms1 created (id=2385087336). GEOM_MIRROR: Device gms1: provider da1s1 detected. GEOM_MIRROR: Device gms1: provider da1s1 activated. GEOM_MIRROR: Device gms1: provider mirror/gms1 launched. WARNING: Expected rawoffset 0, found 63 app1# disklabel -r /dev/mirror/gms1 # /dev/mirror/gms1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 71119692 63 unused 0 0 # "raw" part, don't edit partition c: partition extends past end of unit disklabel: partition c doesn't start at 0! disklabel: partition c doesn't cover the whole unit! disklabel: An incorrect partition c may cause problems for standard system utilities da1s1 still shows: app1# disklabel -r da1s1 # /dev/da1s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 71119692 0 unused 0 0 # "raw" part, don't edit I feel I'm missing something blatantly obvious here. Is that offset of 63 something to do with metadata? Have I not left any space for metadata that I should have done? I was hoping that I'd be able to end up applying this gmirror command to an existing disk with live data on it, and then attach a free disk to achieve a complete mirror from an existing system? Are these warnings about partition c actually ignorable, or even normal? This system is 5.3-BETA5, built moments ago, and supped just before that. Appreciate any help. -- Chris