Date: Thu, 16 Feb 2006 09:29:12 -0500 From: Joe Auty <joe@netmusician.org> To: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> Cc: freebsd-questions@freebsd.org Subject: Re: core dump with dump command SOLVED Message-ID: <D22C96E6-2B6F-40D6-BB93-6D80C83C8F27@netmusician.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <joe@netmusician.org> 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D22C96E6-2B6F-40D6-BB93-6D80C83C8F27>