# [EMAIL PROTECTED] / 2004-08-18 22:51:05 +0400:
> On Wed, Aug 18, 2004 at 07:52:50AM +0200, Roman Neuhauser wrote:
> > I have problems dump|restoring to a new disk.
> >
> > Procedure:
> >
> > shutdown now
> > /sbin/fdisk -Iv ad1
> > /sbin/disklabel -r ad1s1
> > /sbin/disklabel -re ad1s1
> > /sbin/newfs /dev/ad1s1e
> > /sbin/swapon -a # 1GB ad0s1b
> > /sbin/mount /dev/ad1s1a /mnt
> > cd /mnt
> > /sbin/dump -0af- /usr | restore -xf-
> > <-- restore reports insufficient memory, asks for permission to abort
> > and dump core (backtrace below)
>
> I expirienced something like this (I don't remember exactly)
> when I had not enough space in /tmp.
You're not the first person to suggest this might be the culprit.
But, /tmp remains the same both in single- and multiuser modes;
notice that I was dumping /usr, and this output:
[EMAIL PROTECTED] ~ 1003:2 > ls -l / | grep -Fe '->'
lrwxr-xr-x 1 root wheel 10 Mar 18 02:08 compat -> usr/compat
lrwxr-xr-x 1 root wheel 8 Mar 18 02:08 home -> usr/home
lrwxr-xr-x 1 root wheel 7 Mar 18 02:08 opt -> usr/opt
lrwxr-xr-x 1 root wheel 11 Jun 27 14:27 sys -> usr/src/sys
lrwxr-xr-x 1 root wheel 7 Mar 18 02:08 tmp -> usr/tmp
lrwxr-xr-x 1 root wheel 7 Mar 18 02:08 var -> usr/var
IOW, if /tmp has enough space in multiuser, what would it cause
to shrink in singleuser? (I tried the dump|restore multiple times
in both modes, with consistent results.)
--
FreeBSD 4.10-STABLE
7:27AM up 23:37, 4 users, load averages: 0.06, 0.05, 0.01
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
