From owner-freebsd-questions Sun Jun 3 2:32:37 2001 Delivered-To: freebsd-questions@freebsd.org Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by hub.freebsd.org (Postfix) with ESMTP id 3033A37B403 for ; Sun, 3 Jun 2001 02:32:32 -0700 (PDT) (envelope-from rene@xs4all.nl) Received: from xs4.xs4all.nl (xs4.xs4all.nl [194.109.6.45]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id LAA02489; Sun, 3 Jun 2001 11:32:30 +0200 (CEST) From: rene@xs4all.nl Received: (from rene@localhost) by xs4.xs4all.nl (8.9.0/8.9.0) id LAA19058; Sun, 3 Jun 2001 11:32:29 +0200 (CEST) Date: Sun, 3 Jun 2001 11:32:29 +0200 To: Bill Moran Cc: freebsd-questions@freebsd.org Subject: Re: restore fails when trying to run from fixit.flp (freeBSD) Message-ID: <20010603113229.G2791@xs4all.nl> References: <20010602124146.A12549@xs4all.nl> <3B18EEB4.B5BFE6C7@iowna.com> <20010602171852.E2791@xs4all.nl> <3B196DB1.408E41B6@iowna.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B196DB1.408E41B6@iowna.com>; from wmoran@iowna.com on Sat, Jun 02, 2001 at 06:50:25PM -0400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I would if I could. but if /usr isn't restored, I can't login to my box because /usr/libexec/getty is missing :( On Sat, Jun 02, 2001 at 06:50:25PM -0400, Bill Moran wrote: > Hmmm ... well, why not restore / and /var, then reboot off the newly > repaired system, then continue on and restore /usr?? > > rene@xs4all.nl wrote: > > > > alas, no way dude ;) > > > > I had <2G on that partition.. > > > > and it's the memdisk (/dev/md0c) that's full, not my target device. > > > > and yes, i'm running it from the proper mounted dir, and ls there returns > > nothing except . and .. before starting :) > > > > any more tips? > > > > On Sat, Jun 02, 2001 at 09:48:36AM -0400, Bill Moran wrote: > > > It seems to me that you had more than 5G worth of data on your /usr > > > part. Remake the partitions to match the original sizes (or bigger) and > > > try the procedure again. > > > > > > -Bill > > > > > > rene@xs4all.nl wrote: > > > > > > > > Hi. I've got a 4.3-stable box for which I'm testing a backup procedure. > > > > > > > > I have 4 disks in the box: > > > > da0 scsi 8G (bootdisk) > > > > da1 scsi 2G > > > > ad0 IDE 10G > > > > ad1 IDE 10G > > > > > > > > I have made a single slice of ad0, ad0s1 and newFSed that, then mounted it > > > > somewhere. > > > > > > > > I have done the following on my running system: > > > > > > > > dump -0ua /mnt/ad0/l0/da0s1a / > > > > dump -0ua /mnt/ad0/l0/da0s1e /var > > > > dump -0ua /mnt/ad0/l0/da0s1f /usr > > > > disklabel da0 | /mnt/ad0/l0/da0.disklabel.txt > > > > dmesg | /mnt/ad0/dmesg.txt > > > > cp /etc/fstab /mnt/ad0/fstab > > > > > > > > This produced the correct files without errors in the /mnt/ad0/ structure > > > > > > > > I then used MSDos to format the da0 disk, simulating a complete failure. > > > > > > > > Now, restoration of my volumes I want to have done via the simplest > > > > procedure possible; I think this is to boot a fixit.flp (after kern.flp > > > > and mfsroot.flp ofcourse) and start a shell. > > > > > > > > So, in this case, I use the installation menu of mfsroot.flp to re-create > > > > the partitions/slices (slightly changed in size, decreased 7G /usr to 5G, > > > > then enlarged / and /var) on the ad0 disk. > > > > > > > > I then newfs'ed those new partitions (da0s1a, da0s1e and da0s1f), and > > > > mounted them as /mnt/da0s1*. > > > > > > > > Restoring the first two volumes, / and /var, is done without problems. I > > > > simply use > > > > cd /mnt/da0s1a && restore -rf /mnt/ad0/l0/da0s1a > > > > and the same for da0s1e ofcourse, they both work without any messages and > > > > re-create files so I guess they work just fine. > > > > > > > > Now, the problem starts with restoring /mnt/da0s1f with > > > > > > > > cd /mnt/da0s1f && restore -rf /mnt/ad0/l0/da0s1f > > > > > > > > the first set of errors I get is > > > > > > > > /: write failed, file system is full > > > > > > > > I get this one quite often, but the process continues anyway, and then > > > > starts outputting a new set of errors: > > > > > > > > warning: '.' missing from directory ./include/ > > > > > > > > or > > > > > > > > warning: '..' missing from directory ./include/ > > > > > > > > Now, a quick look at df output shows me that my / filesystem is indeed > > > > full. mount shows me that / is in fact /dev/md0c which is a 2.88M ramdisk. > > > > > > > > I thought of remounting / as /dev/da0s1a (since its restored already), but > > > > ofcourse(?) I can't remount a filesys that's in use...(?) > > > > > > > > I would appreciate some clues here, I never thought that the > > > > backup-restore procedure of fbsd would be so complicated :(( > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > -- > > > If a bird in the hand is worth two in the bush, > > > then what can I get for two hands in the bush? > > > > > -- > If a bird in the hand is worth two in the bush, > then what can I get for two hands in the bush? > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message