Date: Wed, 15 Feb 2006 09:53:29 -0500 From: Joe Auty <joe@netmusician.org> To: freebsd-questions@freebsd.org Subject: Re: core dump with dump command in single user mode Message-ID: <5681BB6E-A511-4790-A8D9-33FBCBA3B800@netmusician.org> In-Reply-To: <44oe19ftis.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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 14, 2006, at 5:46 PM, Lowell Gilbert wrote: > Joe Auty <joe@netmusician.org> writes: > >> On Feb 14, 2006, at 9:08 AM, Lowell Gilbert wrote: >> >>> Joe Auty <joe@netmusician.org> writes: >>> >>>> Hello, >>>> >>>> Following the instructions here: http://www.unixcities.com/howto/ >>>> index.html I did a: >>>> >>> Those directions are a little outdated, but the problem is really >>> just >>> that you didn't follow the directions closely enough: >>> >>>> dump -0f - /usr | restore -rf - /backup/usr >>> >>> should have been more like >>> >>> dump -0f - /usr | (cd /backup/usr;restore -xf - ) >> >> >> Okay, I'm still getting: >> >> >> no space left in string table >> abort? >> >> If I say "n", it just core dumps.... > > Funny, I can't find that message in the source for dump at all. > The message, in -STABLE, is "Do you want to abort dump?". > > I also can't seem to find the string table error message, but I may > just have failed to search the right library so far. > > Are you running something before 5.2? > I'm running 5.4. Perhaps restore is generating this particular error message? I don't know. >> Any other suggestions? > > Plenty. If there are no special files (fifos, etc.) on the disk, any > archiver will do it. e.g., tar(1) > >> Would using "dd" be a valid workaround to >> cloning my disk? > > Sure. If you really want a *clone* of the disk, it's a good option. > If having the same data files in the same filestructure would do, then > copying other attributes is overkill. 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? > >> 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? ----------- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org joe@netmusician.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5681BB6E-A511-4790-A8D9-33FBCBA3B800>