From owner-freebsd-questions@FreeBSD.ORG Mon Oct 4 16:53:11 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 140F916A4CE for ; Mon, 4 Oct 2004 16:53:11 +0000 (GMT) Received: from ns1.tiadon.com (SMTP.tiadon.com [69.27.132.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5FA543D31 for ; Mon, 4 Oct 2004 16:53:10 +0000 (GMT) (envelope-from kdk@daleco.biz) Received: from [69.27.131.0] ([69.27.131.0]) by ns1.tiadon.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 4 Oct 2004 11:56:47 -0500 Message-ID: <41617FF3.9030407@daleco.biz> Date: Mon, 04 Oct 2004 11:53:07 -0500 From: "Kevin D. Kinsey, DaleCo, S.P." User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040712 X-Accept-Language: en-us, en MIME-Version: 1.0 To: questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 Oct 2004 16:56:47.0916 (UTC) FILETIME=[22EBF6C0:01C4AA33] Subject: Magical HDD Space Doubling! 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, 04 Oct 2004 16:53:11 -0000 The other day I decided to dispose of a drive's worth of WinNT data in order to make more FreeBSD machines in the world (cheer!) In the past I've often used sysinstall for this purpose, so I decided to try the other method suggested by the handbook. I think I got a little funky with bsdlabel, though. Check this out: % dmesg | grep ad GEOM: create disk ad0 dp=0xc5f54660 ad0: 38166MB [77545/16/63] at ata0-master UDMA100 GEOM: create disk ad1 dp=0xc5f54360 ad1: 190782MB [387621/16/63] at ata0-slave UDMA100 GEOM: create disk ad3 dp=0xc6020960 ad3: 38166MB [77545/16/63] at ata1-slave UDMA33 Mounting root from ufs:/dev/ad0s1a Note that both ad1 and ad3 report 38166 MB disks. Now, the only thing I intended to be different on the new disk (ad3) was that it be "dangerously dedicated" and have its own /tmp partition (ad1 has tmp on /). However: % df -h Filesystem Size Used Avail Capacity Mounted on /dev/ad0s1a 989M 151M 759M 17% / devfs 1.0K 1.0K 0B 100% /dev /dev/ad0s1e 34G 20G 11G 66% /usr /dev/ad0s1d 989M 275M 635M 30% /var /dev/ad1s1d 180G 60G 106G 36% /backup /dev/ad3a 36G 614M 33G 2% /mnt /dev/ad3b 496M 29M 427M 6% /mnt2 /dev/ad3d 989M 273M 637M 30% /mnt3 /dev/ad3e 34G 20G 11G 66% /mnt4 So, ad3 is ~72GB?? ... I'd gladly take the extra space, but it can't really be there, can it? Here's the bsdlabel output, and a uname. Can anyone tell me what I did wrong (other than the obvious, being "proceeding to use bsdlabel without a thorough handle on what I was doing ... :-o ) % sudo bsdlabel ad0s1 # /dev/ad0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 2097152 0 4.2BSD 2048 16384 28552 b: 1048576 2097152 swap c: 78156162 0 unused 0 0 # "raw" part, don't edit d: 2097152 3145728 4.2BSD 2048 16384 28552 e: 72913282 5242880 4.2BSD 2048 16384 28552 % sudo bsdlabel ad3 # /dev/ad3: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 2097152 0 4.2BSD 2048 16384 28552 b: 1048576 2097152 swap c: 78165360 0 unused 0 0 # "raw" part, don't edit d: 2097152 3145728 4.2BSD 2048 16384 28552 e: 72913282 5242880 4.2BSD 2048 16384 28552 The only difference in the labels is ad3c, which I increased manually (trial & error) because bsdlabel kept complaining "partition c doesn't cover entire unit" until I got up to 78165360 ... %uname -aFreeBSD archangel.daleco.biz 5.2.1-RELEASE-p3 FreeBSD 5.2.1-RELEASE-p3 #2: Fri Apr 23 16:39:28 CDT 2004 root@archangel.daleco.biz:/usr/obj/usr/src/sys/GENERIC i386 [Gee, I thought I'd built world since then...] Kevin Kinsey DaleCo, S.P.