Moving a disk using wrong network device

zBrain

Renowned Member
Apr 27, 2013
38
0
71
I'm moving virtual disks from a FreeNAS box to local-zfs storage.

The freeNAS machine I'm migrating from is on 10.0.1.108/24 (storage network)

The machine I'm migrating to has:
vmbr0: 10.0.0.111/24 (management network)
vmbr1: (public ip + gateway)
bond0: 10.0.1.111/24 (storage network)

In my datacenter options I selected 10.0.0.114/24 for the migration network (not sure if this affects disk move?)

So I'd expect the disk move to be done via bond0 - but its going through vmbr1. I'm not even sure how that's possible...but it's happening.

Can anyone tell me how to force it to use bond0?
 
I've done some more digging and this is only more confusing and frustrating.

The source disk is a LVM device on top of iSCSI. Trying from another node where enp6s0 is a 10GB link...

# iscsiadm --mode node
10.0.1.108:3260,-1 iqn.2005-10.org.freenas.ctl:data-c-iscsitarget

# ip r
default via (public ip) dev vmbr1 onlink
10.0.0.0/24 dev vmbr0 proto kernel scope link src 10.0.0.113
10.0.1.0/24 dev enp6s0 proto kernel scope link src 10.0.1.113
(public IP)/26 dev vmbr1 proto kernel scope link src xyz

Sometimes if I start moving the disk it will use vmbr0 and give me half decent speed for an hour or so, then it switches(!) to vmbr1 and the speed drops to 3MB/s.

It never uses enp6s0 though. Same thing if I try doing a backup...I've tried doing it online, offline...I really need it to use the correct network device!

Separate question: is there a way I could dump this virtual disk to a file and re-import it? I'm having a hard time picturing how. FreeNAS has it sitting on ZFS then Proxmox layered LVM on top over iSCSI.