From owner-freebsd-questions@FreeBSD.ORG Mon Dec 6 01:14:29 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8322B16A4D8 for ; Mon, 6 Dec 2004 01:14:29 +0000 (GMT) Received: from rrzmta2.rz.uni-regensburg.de (rrzmta2.rz.uni-regensburg.de [132.199.1.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id D50BF43D79 for ; Mon, 6 Dec 2004 01:14:28 +0000 (GMT) (envelope-from markus.hoenicka@mhoenicka.de) Received: from rrzmta2.rz.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 71C481177B for ; Mon, 6 Dec 2004 02:17:04 +0100 (CET) Received: from tipi.mininet (rrzras2-87.rz.uni-regensburg.de [132.199.209.87]) by rrzmta2.rz.uni-regensburg.de (Postfix) with ESMTP id 82B9B11773 for ; Mon, 6 Dec 2004 02:17:03 +0100 (CET) X-Mailer: emacs 21.2.1 (via feedmail 8 I); VM 7.03 under Emacs 21.2.1 From: "Markus Hoenicka" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16819.45605.329220.990169@tipi.mininet> Date: Mon, 6 Dec 2004 02:13:09 +0100 To: freebsd-questions@freebsd.org In-Reply-To: <20041206000639.GP92212@wantadilla.lemis.com> References: <16819.39297.635859.406944@tipi.mininet> <20041206000639.GP92212@wantadilla.lemis.com> Subject: Re: vinum limits disk size to 255MB X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 01:14:29 -0000 Greg 'groggy' Lehey writes: > You don't say whether you're using vinum or gvinum. I've never seen > this problem before, but if you're getting incorrect subdisk sizes, > try specifying them explicitly: > > sd length 35840952s drive ibma > > I wonder whether the problem is related to specifying the size as 0m > instead of 0. It shouldn't be. > Actually I've never heard of gvinum, so I'm pretty sure we're looking at vinum here. Looks like this is an odd pilot error. If I label disks from within sysinstall and on the command line, one tool apparently doesn't know what the other is doing. This must be a gross misunderstanding on my side of how these tools work. Using bsdlabel to set the partition sizes apparently is not sufficient. To make a long story short, I went back to sysinstall, created a partition using the full disk, then went to bsdlabel -e to turn the partition into type vinum. Now I get the full capacity. I still can't make a raid5 out of these drives. I'm still fiddling and will get back to the list if I can't figure this out myself. Thanks anyway for your prompt answer. Markus -- Markus Hoenicka markus.hoenicka@cats.de (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de