From owner-freebsd-current@FreeBSD.ORG Mon Dec 8 13:59:42 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 1577816A4CE for ; Mon, 8 Dec 2003 13:59:42 -0800 (PST) Received: from rdsnet.ro (smtp.rdsnet.ro [62.231.74.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4662143D20 for ; Mon, 8 Dec 2003 13:59:28 -0800 (PST) (envelope-from itetcu@apropo.ro) Received: (qmail 23303 invoked from network); 8 Dec 2003 21:59:14 -0000 Received: from unknown (HELO it.buh.cameradicommercio.ro) (81.196.25.19) by mail.rdsnet.ro with SMTP; 8 Dec 2003 21:59:14 -0000 Date: Tue, 9 Dec 2003 00:00:04 +0200 From: Ion-Mihai Tetcu To: Doug White Message-Id: <20031209000004.36d4a1b9.itetcu@apropo.ro> In-Reply-To: <20031208123533.N15361@carver.gumbysoft.com> References: <20031208181611.1a358bb5.itetcu@apropo.ro> <20031208123533.N15361@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: Mon, 08 Dec 2003 21:59:42 -0000 On Mon, 8 Dec 2003 12:38:32 -0800 (PST) Doug White wrote: > On Mon, 8 Dec 2003, Ion-Mihai Tetcu wrote: > > > I've sent the mesage on question with no reply so I'm trying my luck > > here. I am able to reproduce both dump/restore and the fsck errors, even > > after a fdisk-ing, labeling and newfs-ing (from the sysinstall). > > > > The nice thing is that everithing seems to be ok (e.g. on new system > > install it comes up and run OK) untill the first unclean shutdown, when > > fsck complaines about the UNEXPECTED SOFT UPDATE INCONSISTENCY. > > I think you caused some major braindamage by copying over a running > system. You should boot the original disks (ad3s2a), re-newfs the ad0 > partitions, mount them (example is /newroot for the a partition, make > directories as needed and mount other partitions), Maybe I wasn't clea. This is what I did: 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. > 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" > edit /newroot/etc/fstab, change entries > > Unmount the new partitions then reboot to the new disks. If it works, > you're all good. If not you have a fallback. I'm writting now using the fallback :) > I'm not sure dump/restore works to disks of different sizes. Again the faq ... http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NEW-HUGE-DISK Am I missing anything here ? -- IOnut Unregistered ;) FreeBSD user