Am 18.12.10 15:54, schrieb eXeC001er:
2010/12/18 Stephan Budach <stephan.bud...@jvm.de
<mailto:stephan.bud...@jvm.de>>
Am 18.12.10 15:14, schrieb Edward Ned Harvey:
From: Stephan Budach [mailto:stephan.bud...@jvm.de]
Ehh. well. you answered it. sort of. ;)
I think I simply didn't dare to overwrite the root zfs on the destination
zpool
with -F, but of course you're right, that this is the way to go.
What are you calling the root zfs on the destination?
You're not trying to overwrite / are you? That would ... admittedly ... not
be so straightforward. But I don't think it's impossible.
The root zfs, to me, is the fs that gets created once you create
the zpool. So, if I create the zpool tank, I also get the zfs fs
tank, no?
Yes, but zfs receive can put received data only to another pool. You
cannot zfs receive to RAW disk
Well, in the end it is of course as Edward pointed out. Imagine a zpool
called tank with 4 ZFS volumes on it:
tank
tank/fs1
tank/fs2
tank/fs3
This sums up to 4 volumes (maybe I should have used volumes, rather then
fs).
I wanted to transfer the complete zpool tank onto another zpool called
backupTank by using zfs send -R t...@snap | zfs recv backupTank, which
raised the error message that I can't overwrite the existing volume.
This can of course be overwritten by using -F, such as that it would
replace everything on backupTank with the contents of tank - this is
what I didn't dare, since for some reason, I thought that the volume
tankBackup would get destroyed, but in the end it's not the volume that
gets destroyed, but it's contents gets overwritten.
Cheers,
budy
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
