Re: Moving to a bigger HD, is dump still the best way - dump problem
Bill wrote: ... Now here is what I did then... # cd /mnt/newr # ../oldr/sbin/dump 0af - /mnt/oldr | restore rf - (the old drive is also openbsd 3.8) This worked like a charm for the root fs Then I tried the var and I got a slew of errors about the disk being full. But its the /dev/rd* drive thats full. I am guessing its the - part of it. Is it because the restore is not grabbing it as fast as the dump is putting it there? ... I don't have time to verify the error that I'm pretty sure you are making, but you are deviating from the FAQ's instructions, in a way that I'm sure you think doesn't matter, but I'm pretty sure it does. Nick.
Re: Moving to a bigger HD, is dump still the best way - dump problem
Hello! On Mon, Jan 09, 2006 at 01:40:19AM -0500, Bill wrote: [...] Now here is what I did then... # cd /mnt/newr # ../oldr/sbin/dump 0af - /mnt/oldr | restore rf - (the old drive is also openbsd 3.8) This worked like a charm for the root fs Then I tried the var and I got a slew of errors about the disk being full. But its the /dev/rd* drive thats full. dump/restore need some space in /tmp. Just mount a mfs to /tmp so that that doesn't fill up the initial ramdisk. When I move to another disk, I boot from the old one to single user, mount the new one unter /mnt and do the dump/restore for all partitions. I just call mount /tmp manually, /etc/fstab has an entry for an mfs based /tmp on my boxen anyway. [...] Kind regards, Hannah.
Re: Moving to a bigger HD, is dump still the best way - dump problem
In message [EMAIL PROTECTED] so spake Hannah Schroeter (hannah): dump/restore need some space in /tmp. Just mount a mfs to /tmp so that that doesn't fill up the initial ramdisk. Or just point the TMPDIR environment variable to a mounted partition with enough space. - todd
