2 msgsrc/UPDATE
6 msgIPW3945ABG -- Support in RELENG 7?
9 msgiwi loses ssid
3 msgHPS USB stack on current will not build any longer
4 msgdevice rue causes kernel panic

moving a zfs pool
\ Volker (7 Jul 2007)
. \ Bernd Walter (8 Jul 2007)
. \ Dan Nelson (8 Jul 2007)

1 msgpanic in _mtx_lock_sleep
5 msgsysutils/xsi not building on -CURRENT with new gcc
3 msgWhat is reason for fixed system data format?
20 msgstatus of 7.0
12 msgZFS leaking vnodes (sort of)
3 msg[panic] _mtx_lock_sleep: recursed on non-recurs...
22 msgRe: ichwd for ICH8
1 msgmini-headsup: about sed(1) breakage (world brok...
1 msgZFS crash with ggate
1 msg[Fwd: Re: [Fwd: Re: ZFS vs Samba Debugging Resu...
5 msgxorg 7.2 locks system in current
8 msgbuildworld error
12 msgFuture of the ie(4) driver
1 msgbuildworld failure (libmd)
Subject:moving a zfs pool
Group:Freebsd-current
From:Volker
Date:7 Jul 2007


 
Hi,

this is more likely currently a theoretical question: How does one
move a zfs pool from one machine to another?

I've done that in the past a lot with ufs filesystems by piping a dump
through an ssh session and restoring on another machine just to move
data to another system. This should also work on a per filesystem
basis when using zfs but isn't there a way to move the whole pool to
another machine (w/o physically moving the hard disk)?

This would be the case when migrating a machine or migrating hard
disks. The zfs export feature doesn't look promising for this or do I
misread some bits? Please don't tell me, 42 is the answer... ;)

I'm missing something I would call 'zpool dump' and 'zpool restore'.

Thanks!

Volker
_______________________________________________
freebsd-current mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe"


© 2004-2008 readlist.com