There is problem during dump/restore.

[Shahin Hasanov]

Thank you Matthew,
I have two HDD da0,da1
da0 is 147GB   - ufs
da1 is 1.1TB    - zfs
I did like bellow:
 
# zpool import -f HASTPOOL
# mount -t zfs HASTPOOL /mnt
# newfs /dev/da0p2
# mkdir /mnt/test 
 # mount /dev/da0p2 /mnt/test
# mkdir /mnt/tmp
# export TMPDIR=/mnt/tmp
# cd /mnt/test
# restore -r -f /mnt/NODE_2.dump 
 
When it gave message I type 'n'
cannot find directory inode 10032011
> > abort? [yn] n
> > cannot find directory inode 10032013
> > abort? [yn] n
# cd ..
# umount /mnt/test
# fsck -t ufs -p /dev/da0p2
# reboot
 
It seems it works
 
Is it normal?
 
 
Best regards
Shahin Hasanov
 
 

 
> Subject: Re: There is problem during dump/restore.
> To: freebsd-questions at freebsd.org
> From: matthew at FreeBSD.org
> Date: Tue, 5 Jan 2016 13:22:04 +0000
> 
> On 2016/01/05 12:32, Shahin Hasanov wrote:
> >  
> > I had server FreeBSD 10.1
> > I make dump:
> > 
> > dump -0 -a -f /home/USER/node2.dump /dev/da0p2
> > 
> > When I trying
> > # restore -r -f /mnt/node2.dump
> > 
> > I was gave error message 
> > 
> > cannot find directory inode 10032011
> > abort? [yn] n
> > cannot find directory inode 10032013
> > abort? [yn] n
> 
> How big is the filesystem you're restoring to compared to the one you
> dumped?
> 
> You did create a new, empty filesystem to restore into, mount that and
> change directory to the mount point before attempting the restore?  And
> you didn't copy the dumpfile 'node2.dump' into the filesystem you're
> attempting to restore to -- 'restore -r' wants a brand new, empty
> filesystem initially?
> 
> Are you using SU+J (Soft Updates + Journalling) on the newly created
> filesystem?  While that's the default for the system installer nowadays,
> it doesn't actually play well with dump/restore.
> 
> 	Cheers,
> 
> 	Matthew
> 
> 
>