From owner-freebsd-questions@FreeBSD.ORG Thu Feb 16 14:29:22 2006 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 F30A416A420 for ; Thu, 16 Feb 2006 14:29:21 +0000 (GMT) (envelope-from joe@netmusician.org) Received: from netmusician.org (netmusician.org [209.67.223.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE60D43D62 for ; Thu, 16 Feb 2006 14:29:16 +0000 (GMT) (envelope-from joe@netmusician.org) Received: from localhost (localhost [127.0.0.1]) by netmusician.org (Postfix) with ESMTP id 0AE60730A4; Thu, 16 Feb 2006 09:29:16 -0500 (EST) Received: from netmusician.org ([127.0.0.1]) by localhost (netmusician.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 41423-03; Thu, 16 Feb 2006 09:29:15 -0500 (EST) Received: from [192.168.0.2] (12-223-193-72.client.insightbb.com [12.223.193.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by netmusician.org (Postfix) with ESMTP id 244EB7309B; Thu, 16 Feb 2006 09:29:15 -0500 (EST) In-Reply-To: <44d5hnqt2k.fsf@be-well.ilk.org> References: <1CFD830B-2CAC-44A9-9120-6CF351FD3EB9@netmusician.org> <443bimav7o.fsf@be-well.ilk.org> <039BD206-0592-4F99-BE9B-CB49310E5BDC@netmusician.org> <44oe19ftis.fsf@be-well.ilk.org> <5681BB6E-A511-4790-A8D9-33FBCBA3B800@netmusician.org> <44d5hnqt2k.fsf@be-well.ilk.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Joe Auty Date: Thu, 16 Feb 2006 09:29:12 -0500 To: Lowell Gilbert X-Mailer: Apple Mail (2.746.2) X-Virus-Scanned: by amavisd-new at netmusician.org Cc: freebsd-questions@freebsd.org Subject: Re: core dump with dump command SOLVED 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, 16 Feb 2006 14:29:22 -0000 Thanks everybody for their help. As it turns out, I guess dump was being starved for memory, as running it while booted into FreeBSD normally using -L to indicate a live filesystem worked just fine. I believe this is because there is an extra swap file available from a normal FreeBSD boot, as specified in my /etc/rc.conf. I'm not sure if my theory completely holds up, but there you have it. Thanks again! I'm up and running... On Feb 16, 2006, at 9:25 AM, Lowell Gilbert wrote: > Joe Auty writes: > >> I'm running 5.4. Perhaps restore is generating this particular error >> message? I don't know. > > It would be hard to tell, without an intermediate disk to write the > data to so you can separate the dump from the restore. You might be > able to trace one of the processes to see, but that requires a bit of > technical knowledge. > >> I may have to go this route, see if I can put together the disk space >> to manage this. Is there a way to get tar to just extract directly to >> a destination directory so I don't have to contend with a single >> large tarball I need to create disk space for? > > Sure. As far as I'm concerned, that's the normal way to copy > directory trees. You just pipe the output of the tar process into > another tar process that un-tars it in another place. > > E.g.: > tar -C ~/work/debugger -cf - . | tar -C temp -xf - > > > >>> >>>> My disk is over a 100 gigabytes, could this be >>>> what >>>> is causing dump to crap out? >>> >>> Could be. Check your memory statistics while you're doing it, >>> and see >>> if you run out of VM. >> >> What is a good strategy for dealing with this possibility, should I >> go down that path? > > Start by watching top(1) while it's running... > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org"