Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 5 Jan 2016 17:39:16 +0400
From:      Shahin Hasanov <shahinhasanov@hotmail.com>
To:        Matthew Seaman <matthew@freebsd.org>, FREEBSD_QUESTION <freebsd-questions@freebsd.org>
Subject:   RE: There is problem during dump/restore.
Message-ID:  <DUB127-W4413B16E22DB29A4F637D9B6F30@phx.gbl>
In-Reply-To: <568BC37C.2010903@FreeBSD.org>
References:  <DUB127-W87D679C1AAA8A0C5276BD8B6F30@phx.gbl>, <568BC37C.2010903@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Thank you Matthew=2C
I have two HDD da0=2Cda1
da0 is 147GB   - ufs
da1 is 1.1TB    - zfs
I did like bellow:
=20
# zpool import -f HASTPOOL
# mount -t zfs HASTPOOL /mnt
# newfs /dev/da0p2
# mkdir /mnt/test=20
 # mount /dev/da0p2 /mnt/test
# mkdir /mnt/tmp
# export TMPDIR=3D/mnt/tmp
# cd /mnt/test
# restore -r -f /mnt/NODE_2.dump=20
=20
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
=20
It seems it works
=20
Is it normal?
=20
=20
Best regards
Shahin Hasanov
=20
=20

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DUB127-W4413B16E22DB29A4F637D9B6F30>