From owner-freebsd-questions@FreeBSD.ORG Wed May 19 23:35:25 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 36C1816A4CE for ; Wed, 19 May 2004 23:35:25 -0700 (PDT) Received: from dns1.popstick.com (dns1.popstick.com [66.37.210.4]) by mx1.FreeBSD.org (Postfix) with SMTP id D5AB043D4C for ; Wed, 19 May 2004 23:35:24 -0700 (PDT) (envelope-from mlists@northglobe.com) Received: (qmail 56266 invoked from network); 20 May 2004 06:34:58 -0000 Received: from unknown (HELO localhost.invalid) (24.147.149.77) by 0 with SMTP; 20 May 2004 06:34:58 -0000 From: Nicholas Basila To: hoe-waa@hawaii.rr.com Date: Thu, 20 May 2004 02:34:58 -0400 User-Agent: KMail/1.6 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405200234.58022.mlists@northglobe.com> cc: freebsd-questions@freebsd.org Subject: Re: /usr out of space 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: Thu, 20 May 2004 06:35:25 -0000 On Thursday 20 May 2004 02:19 am, hoe-waa@hawaii.rr.com wrote: > Aloha Nicholas > Thanks for responding. I had just received a hint > about growfs and while reading that I found out > about newfs. I have indeed performed the newfs and > can now mount /dev/da1s4f. > Would it be possible to use growfs to add the new > slice to /usr? It is possible to use growfs, but in your case - more complicated, as you have /usr and the new /usr in two different slices. You'd have to resize the slice with fdisk, then use disklabel and growfs. > If not, I will follow your instructions in this > email. > Thanks again. > Robert > > > On Wednesday 19 May 2004 08:17 pm, hoe-waa@hawaii.rr.com wrote: > > > When I tried using bsdlabel without any options I got an error. > > > So I then did a "bsdlabel -w da1s4" and the a "bsdlabel -e da1s4" > > > and edited what I believe are the correct numbers for this slice. > > > Now when I do the "bsdlabel da1s4" with no options, I get > > > > > > # /dev/da1s4: > > > 8 partitions: > > > # size offset fstype [fsize bsize bps/cpg] > > > c: 8980335 0 unused 0 0 # "raw" > > > > part,> don't edit f: 8980319 16 4.2BSD 2048 16384 > > 28552 > > > > > I still get the above error when trying to mount this slice. > > > > > > To sum it up. > > > > > > Is it possible to mount, copy and change the /usr partition? > > > > > > If so, how do I correct the super block problem so I can mount? > > > > > > Or, is there a much easier way and I have been spinning my wheels > > > > for> the last 6 hours? > > > > Perhaps I've missed a step, but it seems that you never did a > > newfs / > > dev/da1s4f. If not, that would be an obvious explanation for the > > incorrect super block error. > > At any rate, it is pretty easy to copy data from usr to a new > > slice and > > change fstab. I do it on occasion. I would recommend making a copy > > of > > fstab that has the da1s4f as the /usr partition. > > I do a tunefs -n enable on the new filesystem device. Then, I boot > > into > > single user mode, mount -ro /usr and mount -rw /newusr (and I even > > mount /var if I need to do editing with vi.) I then tar or copy the > > files over (dump works, too). After all that's done, umount /usr > > and > > umount /newusr. Copy the new version of fstab to /etc/fstab, and > > try a > > mount /usr or mount -a. If there are no errors, you should be able > > to > > hit control-d and finish the boot procedure. > > > > > > Nicholas > > > > > TIA > > > > > > Robert > > > > > > P.S. Here's what bsdlabel on da1s2 looks like; > > > > > > bsd-desktop# bsdlabel da1s2