From owner-freebsd-questions@FreeBSD.ORG Thu Jun 2 15:11:53 2005 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 C07CB16A41C for ; Thu, 2 Jun 2005 15:11:53 +0000 (GMT) (envelope-from jerrymc@clunix.cl.msu.edu) Received: from clunix.cl.msu.edu (clunix.cl.msu.edu [35.9.2.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82A3E43D49 for ; Thu, 2 Jun 2005 15:11:53 +0000 (GMT) (envelope-from jerrymc@clunix.cl.msu.edu) Received: from clunix.cl.msu.edu (localhost [127.0.0.1]) by clunix.cl.msu.edu (8.12.10+Sun/8.12.2) with ESMTP id j52FBqJF024350; Thu, 2 Jun 2005 11:11:52 -0400 (EDT) Received: (from jerrymc@localhost) by clunix.cl.msu.edu (8.12.10+Sun/8.12.2/Submit) id j52FBpKK024349; Thu, 2 Jun 2005 11:11:51 -0400 (EDT) From: Jerry McAllister Message-Id: <200506021511.j52FBpKK024349@clunix.cl.msu.edu> To: vizion@vizion.occoxmail.com (Vizion) Date: Thu, 2 Jun 2005 11:11:51 -0400 (EDT) In-Reply-To: <200506020644.17257.vizion@vizion.occoxmail.com> X-Mailer: ELM [version 2.5 PL7] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: /var too small [was Gap of years = loss of memory!!] 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: Thu, 02 Jun 2005 15:11:54 -0000 > > On Thursday 02 June 2005 06:16, the author Jerry McAllister contributed to > the dialogue on- > Re: /var too small [was Gap of years = loss of memory!!]: > ... > >> (c) I have therefore bought a new 200G SATA drive to add to the system. > >> (d) I wish to allocate 40G to /var and > >> (e) 160G to /dev > >> (f) rename /var to /var.old > >> (g) move /var.old to /var > >> (h) have /var.old mounted as /logs > >> (i) At the same time I also propose increasing memory from 1G to 2G which > >> will > > > >You do not allocate anything to /dev. That is a special directory > >just for devices. Do you really mean something else? > > Yes its my abbreviation for developer!! I must be careful not to do /dev -- > thanks for drawing my attention to that one!! > > I really appreciate yr help. > > Leaving aside the SATA issues about SATA1 & SATA2 could you possibly check > over my proposed fstab entries below? Didn't see any new fstab in this message. The old one you show seems to have all filesystems on disk 4 I don't see anything for the new disk. If that comes out to be disk 6, then it would probably want to mount ad6s1e as /var and maybe ad6s1f as /devel or something like that. Since I do the fdisk, disklabel and newfs by hand on additional disks, I have never assumed anything about how sysinstall treats fstab in subsequent disk additions. ////jerry > > > >As for moving the /var partition: > ... > > cd /var > > rm /var.tar > > > Got it = a good plan to me > Thanks again > David > > > > > >As for below, I can't tell you about shuffling drives on a SATA. > >Hopefully someone else knows that. > > > >////jerry > > > >> hopefully speed up my compiling a little. > >> > >> OK so far .. now > >> If I put the new drive onto SATA 1 with the exiting drive remaining on > >> SATA2 the bios expects to boot from CD. Currently the bios is set to boot > >> from HDD0 but if I change the bios to HDD1 it makes no difference. The > >> system does not boot at all. > >> > >> Unless I have missed something it seems the bios cannot be set to allow > >> boot from SATA2 if a drive is present on SATA1. > >> > >> If I put the existing drive onto SATA 1 with the new drive onto SATA2 then > >> the root mount fails. The existing drive appears to be recognized as ad4 > >> so if my recollection is correct the first step would be to alter > >> /etc/fstab to read: > >> > >> /dev/ad4s1b none swap sw 0 0 > >> /dev/ad4s1a / ufs rw 1 1 > >> /dev/ad4s1e /tmp ufs rw 2 2 > >> /dev/ad4s1f /usr ufs rw 2 2 > >> /dev/ad4s1d /var ufs rw 2 2 > >> /dev/acd0 /cdrom cd9660 ro,noauto 0 0 > >> > >> and the system should mount OK??? > >> IS that correct? > >> I want to get this right first time (if possible!!) > >> > >> Then presumably I can > >> (a) use sysinstall to add the new drive which should presumably mount as > >> ad6? (b) Create partition ad6s1a (+/-40g) > >> (c) Create partition ad6s1b (+- 160G)