On February 22, 2009 8:03:38 PM -0600 David Dyer-Bennet <d...@dd-b.net>
wrote:
On Sun, February 22, 2009 18:11, Frank Cusack wrote:
Did you see my other thread on this specific topic? You can't backup
the root pool using zfs send -R | zfs recv.
Nope, somehow missed the import of that.
I'm only trying to back up the rpool/export/home portion of the root pool;
is that still impossible?
Because so far as I can tell, *that* part is working; it's adding a second
fs that I'm having trouble with.
In the example I posted, this bit WORKED in one case:
# zfs create bup-ruin/fsfs/rpool
# zfs send -R rpool/export/h...@bup-20090216-044512utc | zfs recv -d
bup-ruin/fsfs/rpool
I'll find that other thread and check up; is it a consistent failure or
intermittent, though?
Intermittent? That would indicate some type of transient problem, not
"can't".
Your example worked because you are "only" replicating a filesystem
within the root pool. This works because after setting the altroot
the new (replicated) filesystem mounts in a different location than
the original.
When you try to backup the '/' part of the root pool, it will get
mounted on the altroot itself, which is of course already occupied.
At that point, the receive will fail.
So far as I can tell, mounting the received filesystem is the last
step in the process. So I guess maybe you could replicate everything
except '/', finally replicate '/' and just ignore the error message.
I haven't tried this. You have to do '/' last because the receive
stops at that point even if there is more data in the stream.
-frank
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
