From owner-freebsd-questions@FreeBSD.ORG Fri Jan 27 15:40:43 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 BB8A116A420 for ; Fri, 27 Jan 2006 15:40:43 +0000 (GMT) (envelope-from johnfhoover@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id A07D843DBF for ; Fri, 27 Jan 2006 15:40:42 +0000 (GMT) (envelope-from johnfhoover@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so383851wxc for ; Fri, 27 Jan 2006 07:40:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=H0gy/KsNfqLKhjlqc/IipYUvxWRM0rmVZ2kegmr5qldhsHTfUO6+lkLvnf11ABdUog0aR6pTLALLlY0/pms+PLosEs21gtZDiv6c2eGS2Ix1axl5cWDFCSPcdNb1/Ni5mM1eVBet+dET6iR3ztoWT3K2irrflmPMeM3bvFWwr94= Received: by 10.70.71.13 with SMTP id t13mr3645516wxa; Fri, 27 Jan 2006 07:40:41 -0800 (PST) Received: by 10.70.105.18 with HTTP; Fri, 27 Jan 2006 07:40:41 -0800 (PST) Message-ID: <573015470601270740o2a8ba0dcs6e3e6257cc4ed737@mail.gmail.com> Date: Fri, 27 Jan 2006 09:40:41 -0600 From: John Hoover To: FreeBSD Mailing List In-Reply-To: <200601271458.k0REwpUj020518@clunix.cl.msu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <573015470601261641s2211b1e8y8b2bafcbe24f0741@mail.gmail.com> <200601271458.k0REwpUj020518@clunix.cl.msu.edu> Subject: Re: Odd Partition/Newfs Question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2006 15:40:43 -0000 > > Added an additional hard drive to an existing setup. > > Then gave the following commands: > > > > bsdlabel -w /dev/ad2 > > newfs -U -O 2 /dev/ad2 > > mount /dev/ad2 /mnt/ad2 > > > > then went about the business of moving and rearranging for having the n= ew disk. > > After the machine was back in production, I saw the odd mount point. > > > > My question is, have I just ended up ignoring the bsdlabel command and = I'm > > using the entire disk as a "raw disk" or is there some set of reasons I= should > > re-bsdlabel and newfs /dev/ad2a this time. > > What do you mean 'odd mount point'. You don't give any information > that would make it seem odd. > > What does doing 'bsdlabel ad2' show you? > Does it seem happy? > Does newfs seem happy? > I didn't include output from bsdlabel, as it didn't show anything unexpecte= d %bsdlabel /dev/ad2 # /dev/ad2: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 490234736 16 unused 0 0 c: 490234752 0 unused 0 0 # "raw" part, don't edit which looked right, the odd part was the fact that I issued newfs /dev/ad2 in place of the usual newfs /dev/ad2a So it looked to me as I just ignored the bsdlabel command and newfs'd the entire disk starting at an offset of 0 instaid of the usual offset of 16 With this being a non boot disk, I wasn't worried about it, I'm expecting that the bsdlabel information will get overwritten by the directory structure sooner or later. Except for forgetting that I have a device with a filesystem and no slices/partitions my concern is that there is some internal bookkeeping issue that I'm not aware of that will cause trouble if I don't have valid label information on the disk= . Oh, I tested it with another disk, the directory entries will overwrite the label information, no real surprise there. John. -- ------------------------------------- John F Hoover johnfhoover@gmail.com