From owner-freebsd-sparc64@FreeBSD.ORG Fri Jun 12 16:08:55 2009 Return-Path: Delivered-To: sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9939E106564A for ; Fri, 12 Jun 2009 16:08:55 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 142528FC26 for ; Fri, 12 Jun 2009 16:08:54 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id n5CG8qtA012626; Fri, 12 Jun 2009 18:08:52 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id n5CG8qGB012625; Fri, 12 Jun 2009 18:08:52 +0200 (CEST) (envelope-from marius) Date: Fri, 12 Jun 2009 18:08:52 +0200 From: Marius Strobl To: Ruben de Groot Message-ID: <20090612160852.GT43137@alchemy.franken.de> References: <20090612110250.GA50214@ei.bzerk.org> <20090612145144.GA11613@alchemy.franken.de> <20090612155810.GA54653@ei.bzerk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090612155810.GA54653@ei.bzerk.org> User-Agent: Mutt/1.4.2.3i Cc: sparc64@freebsd.org Subject: Re: problem with sunlabel/gpart X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2009 16:08:55 -0000 On Fri, Jun 12, 2009 at 05:58:10PM +0200, Ruben de Groot wrote: > > Hi Marius, > > On Fri, Jun 12, 2009 at 04:51:44PM +0200, Marius Strobl typed: > > On Fri, Jun 12, 2009 at 01:02:50PM +0200, Ruben de Groot wrote: > > > > > > I wonder if somebody can explain this: > > > In a netra X1 I have 2 identical 150GB disks. One was partitioned by > > > sysinstall like this: > > > > > > # sunlabel ad0 > > > # /dev/ad0: > > > text: FreeBSD149G cyl 47955 alt 2 hd 16 sec 63 > > > bytes/sector: 512 > > > sectors/cylinder: 1008 > > > sectors/unit: 48338640 > > > > > > 8 partitions: > > > # > > > # Size is in sectors. > > > # Offset is in cylinders. > > > # size offset > > > # ---------- ---------- > > > a: 1049328 0 > > > b: 2097648 1041 > > > c: 48338640 0 > > > d: 4195296 3122 > > > e: 1049328 7284 > > > f: 33555312 8325 > > > g: 104858208 41614 > > > h: 165774672 145640 > > > > > > Notice that the c partition is smaller than the entire disk. Trying > > > to copy this partition scheme to ad1 using sunlabel fails with: > > > > > > sunlabel: partition g extends past end of disk > > > > > > gpart shows: > > > > > > morninglightmountain# gpart show ad0 > > > => 0 48338640 ad0 VTOC8 (149G) > > > 0 1049328 1 !0 (512M) > > > 1049328 2097648 2 !0 (1.0G) > > > 3146976 4195296 4 !0 (2.0G) > > > 7342272 1049328 5 !0 (512M) > > > 8391600 33555312 6 !0 (16G) > > > 41946912 104858208 7 !0 (50G) > > > 146805120 165774672 8 !0 (79G) > > > > > > morninglightmountain# gpart show ad1 > > > => 0 48338640 ad1 VTOC8 (149G) > > > 0 48338640 - free - (23G) > > > > > > Off course, I could just use sysinstall again to partition the second > > > disk, but I'm curious as to why this is happening. > > > > > > > Hrm, are/were there existing labels on both ad0 and ad1 > > from a previous OS installation which limit their sizes > > to 24GB? What version of FreeBSD is this? > > > uname -a > FreeBSD morninglightmountain.hacktor.net 8.0-CURRENT FreeBSD 8.0-CURRENT #2: Mon Apr 27 22:37:12 UTC 2009 root@morninglightmountain.hacktor.net:/usr/obj/usr/src/sys/MORNINGLIGHTMOUNTAIN sparc64 > > I did a "dd if=/dev/zero of=/dev/ad1 bs=1m count=1", but that doesn't change anything. > > writing a new label does not help either : > > morninglightmountain# sunlabel -w ad1 auto > morninglightmountain# gpart show ad1 > => 0 48338640 ad1 VTOC8 (149G) > 0 48338640 - free - (23G) > Have you tried to reboot between overwriting the old label and writing a new one? What's the verbose dmesg output regarding these disks? Marius