From owner-freebsd-current@FreeBSD.ORG Wed Dec 10 02:33:08 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A127516A4CE for ; Wed, 10 Dec 2003 02:33:08 -0800 (PST) Received: from rdsnet.ro (smtp.rdsnet.ro [62.231.74.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F93F43D13 for ; Wed, 10 Dec 2003 02:32:59 -0800 (PST) (envelope-from itetcu@apropo.ro) Received: (qmail 8428 invoked from network); 10 Dec 2003 10:32:58 -0000 Received: from unknown (HELO it.buh.cameradicommercio.ro) (81.196.25.19) by mail.rdsnet.ro with SMTP; 10 Dec 2003 10:32:58 -0000 Date: Wed, 10 Dec 2003 12:33:51 +0200 From: Ion-Mihai Tetcu To: Doug White Message-Id: <20031210123351.18326f80.itetcu@apropo.ro> In-Reply-To: <20031209161412.X25346@carver.gumbysoft.com> References: <20031208181611.1a358bb5.itetcu@apropo.ro> <20031209000004.36d4a1b9.itetcu@apropo.ro> <20031209161412.X25346@carver.gumbysoft.com> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: fsck sig 11 (cannot alloc 4216257920 bytes for inoinfo) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 10:33:08 -0000 On Tue, 9 Dec 2003 16:16:16 -0800 (PST) Doug White wrote: > On Tue, 9 Dec 2003, Ion-Mihai Tetcu wrote: > > > Maybe I wasn't clea. This is what I did: > > You weren't :) Well, I guess I should use more often sleep(1) :) > > 1. Booted from CDROM, newfs, install minimal, etc. > > > > 2. Booted from ad0 to see the system up. > > > > 3. Booted from ad3 and dump/restore the ad3 partitions to ad0 using the > > -L swich for dump, as the partition ad3 partition where mounted. > > sounds good. > > > > then copy the data over > > > using tar instead of dump/restore. Tar like this should be close enough: > > > > > > tar -C / -cpf - | tar -C /newroot/ -xpvf - > > > > The FAQ explicitly says not to use tar but dump/restore. "You should > > never use anything but dump(8) and restore(8) to move the root > > filesystem" > > Thats only if you care about hardlinks and file flags (schg). It doesn't > cause a wrecked system, though. I know I is not supposed to break something that deep. > > > > edit /newroot/etc/fstab, change entries > > Did you remember to do this? If not you may have been fscking with the > wrong fsck, and fsck from 4.x will trip over a UFS2 filesystem that a 5.x > install would have created. The system on my small HDD - ad3 is an 5.1-RELEASE-p11 (it was p10 at that time but that doesn't make any differnce). I've used sysinstall from a 5.1R CD-ROM. The rest of the work was done booting from ad3 - 5.1-RELEASE-p10. This includes fsck-ing and I am not aware of anythingthat will prevent a fsck from p10 to work on a 5.1R filesystem. I wanted to duplicate my working system cvsup and try 5.2BETA while keeping a working system on my small HDD - that's one ofthe reasons I wanted to put /home on it one partition. -- IOnut Unregistered ;) FreeBSD user