Migration questions

[danb35]

I'm running FreeNAS 9.2.1.5, having incrementally upgraded over the last couple of years from 8.something, and my zpool is nearing its capacity. Since I created the pool several versions ago, I'm getting the daily warning about 512-byte sector sizes on my 4096-byte-sector drives. I have a few drives on order to increase capacity, and I'm thinking the following procedure will get me running with a larger pool, proper sector size, no loss of data, and everything else working:

1. Create a new pool on the new disks, call it newpool for this example
2. Replicate oldpool to newpool
3. Detach oldpool, marking drives as new
4. Using the ZFS volume manager, add the old drives to the new pool
5. Either rename newpool to oldpool, or edit shares to point to the corresponding locations on newpool

For the ZFS replication, it looks like I should be able to just do

Code:

# zfs send oldpool@last_auto_snapshot | zfs recv newpool

Does this make sense? Am I missing something in this plan?

 

[cyberjock]

Nope, that plan is pretty much it!

Note: if you want to keep any jails you have, you'll want to rename the oldpool to newpool. Otherwise you'll have to delete the jails before destroying oldpool otherwise the jail entries will be orphaned in 9.2.1.5.

 

[danb35]

So no flags necessary on the zfs send or zfs recv commands? The search results I'm finding are a little inconsistent on that point.

I have a plugin jail with Transmission 2.82, but I could just as easily recreate it. I have another entry under installed plugins for Transmission 2.77 which doesn't appear to have an associated jail, but I can't delete it--when I try to, I get "

Error: The plugins jail is not running, start it before proceeding"​

 

[cyberjock]

I don't believe so. I haven't tried to do pool to pool locally in a very long time though.

If it doesn't work I'm sure a little googling will help you figure it out.

 

[danb35]

Great, I'll give it a shot once I get the hardware. Thanks for the help!

 

[danb35]

OK, I have the hardware, and I've tested it. I tested the procedure with a USB drive just to see how it would work, and it seems to have worked just fine. Now, though, I'm having problems. I ran

Code:

# zfs snapshot -r zfs1@snap1
# zfs send -R zfs1@snap1 | zfs recv tank

...and the result was, repeatedly:

Code:

warning: cannot send 'zfs1@auto-20140603.0840-2w': Broken pipe
TIME        SENT   SNAPSHOT
warning: cannot send 'zfs1@auto-20140603.0845-2w': Broken pipe
TIME        SENT   SNAPSHOT
warning: cannot send 'zfs1@auto-20140603.0850-2w': Broken pipe
TIME        SENT   SNAPSHOT
warning: cannot send 'zfs1@auto-20140603.0855-2w': Broken pipe
TIME        SENT   SNAPSHOT
warning: cannot send 'zfs1@auto-20140603.0900-2w': Broken pipe
TIME        SENT   SNAPSHOT
warning: cannot send 'zfs1@auto-20140603.0905-2w': Broken pipe

Permissions are 777 on both /mnt/zfs1 and /mnt/tank. What am I missing here?

 

[danb35]

Never mind, think I've got it figured out. I'd created tank first on a new FreeNAS installation, and it must have created the .system dataset on there. I removed/destroyed the tank pool, rebooted, recreated it, and was then able to (start) running the replication. I'll be interested to see how long it takes to run, there's ~2.5 TB of data to move.

 

[cyberjock]

When I did replication for 22TB I hit near linespeed for more than 95% of the time. ;)

 

[danb35]

The send/receive ran without issues, though for several hours. I then did another snapshot and an incremental send/receive (which only took a few minutes). Conveniently, this thread just surfaced:
http://forums.freenas.org/index.php?threads/how-to-copy-one-pool-into-another.16653/#post-120073
...and that procedure worked perfectly for me. Thanks for the help!