From owner-freebsd-questions@FreeBSD.ORG Mon Jun 4 19:58:08 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6CB4F106564A for ; Mon, 4 Jun 2012 19:58:08 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from nightmare.dreamchaser.org (nightmare.dreamchaser.org [12.32.44.142]) by mx1.freebsd.org (Postfix) with ESMTP id 30CC58FC15 for ; Mon, 4 Jun 2012 19:58:07 +0000 (UTC) Received: from breakaway.dreamchaser.org (breakaway.dreamchaser.org. [12.32.36.73]) by nightmare.dreamchaser.org (8.13.6/8.13.6) with ESMTP id q54JvxPr003202; Mon, 4 Jun 2012 13:57:59 -0600 (MDT) (envelope-from freebsd@dreamchaser.org) Message-ID: <4FCD1347.9060209@dreamchaser.org> Date: Mon, 04 Jun 2012 13:57:59 -0600 From: Gary Aitken User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120528 Thunderbird/12.0.1 MIME-Version: 1.0 To: Polytropon References: <4FCCBDF4.1030008@dreamchaser.org> <20120604164244.81e24528.freebsd@edvax.de> In-Reply-To: <20120604164244.81e24528.freebsd@edvax.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (nightmare.dreamchaser.org [12.32.36.65]); Mon, 04 Jun 2012 13:58:00 -0600 (MDT) Cc: FreeBSD Mailing List Subject: Re: bsdlabel geometry params X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@dreamchaser.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 19:58:08 -0000 On 06/04/12 08:42, Polytropon wrote: >> In step #4, bsdlabel gives you a label with zeros for fsize, bsize, bps/cpg >> Is it necessary to fill these in, or is there a way to get some >> reasonable defaults? >> "newfs -N" will give you numbers for bsize and fsize, but what about bps/cpg? >> >> What does the install process do for this step? I don't remember >> ever having to deal with it. > > Maybe it's bit overcomplicated. I assume as you're creating > /dev/da1s1e here (non-boot volume on 1st slice, which would > be /dev/da1s1a instead), so basically you're creating a kind > of "data disk" (one full disk, not bootable). Actually, no. That was a cut and paste from the handbook, IIRC. The actual disk will have a backup system and another partition for cron dump files. I don't quite understand the relationship between the params in the label and the filesystem. My impression was that the params in the label for a filesystem were mandatory, but it appears not all of them are. It seems like there should be a cmd to run to get reasonable starting point numbers. If you don't have anything to go on, you could easily stick something in there that's worse than what a default would be.