From owner-freebsd-questions Wed Sep 20 20: 8:36 2000 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (zoom0-123.telepath.com [216.14.0.123]) by hub.freebsd.org (Postfix) with SMTP id 5A77837B423 for ; Wed, 20 Sep 2000 20:08:27 -0700 (PDT) Received: (qmail 68111 invoked by uid 100); 21 Sep 2000 03:07:50 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14793.31622.653689.3398@guru.mired.org> Date: Wed, 20 Sep 2000 22:07:50 -0500 (CDT) To: David Banning Cc: questions@freebsd.org Subject: Re: install new drive problem In-Reply-To: <82345575@toto.iv> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Banning writes: > I want to replace my 3.4 gig drive with a new 20 gig drive > I just bought. > > While I'm actually running 4.0 Stable - I used my FreeBSD 2.2.8 old > cdrom set to install the file systems and set as bootable. > > Then I booted from my 3.4 gig drive, mounted my 20 gig drive > and commenced copying all files over with "cp -R" to the individual > file systems. > > There are two problems. One is - the file systems on the new drive fill up > too quickly, and problem 2: the new 20 gig drive won't boot. You have to install a boot block on the new drive by hand. Either boot0cfg or fdisk can do that for you, depending on which boot block you want installed. > Here is what df shows; > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/wd1s1a 87055 38184 41907 48% / > /dev/wd1s1f 2971838 2044310 689781 75% /usr > /dev/wd1s1e 58031 9332 44057 17% /var > procfs 4 4 0 100% /proc > /dev/wd0s1a 98479 40240 50361 44% /newroot > /dev/wd0s1f 19048854 7380208 10144738 42% /newusr > /dev/wd0s1e 98479 9314 81287 10% /newvar > > you can see that although the new file systems contain the exact > same stuff, percentage-wise they take up too much space on the drive. > (eg. 75% of say 3.2 gigs (/usr) should not be 42% of say 18.5 > gigs (/newusr), given that it's the same content) It's not at all clear that the new files "contain the exact same stuff". Check the "used" column. /usr/ goes from ~204 meg to ~738 meg. The copy got screwed up. I'd recommend newfsing those file systems, and doing something like: # cd /newusr # dump 0uaf - /usr | restore xf - and repate for /var and /. > I realize I'm going about this in a rather self-made way but I couldn't > find any example of this in my FreeBSD book (bought with 2.2.8) > and I didn't want to bother you folks without first putting in some > effort myself. There aren't any writeups. There probably should be.