FreeNAS Corral, what the hell...where be my cloning capability

[whitey]

Evening all! Here's the story...I used to rely on cloning snapshots from time to time on FreeNAS 9.x based systems, by all means I don't see it anymore on FreeNAS Corral...sure the HELL hope that didn't go bye-bye.

Here is what I found high level, someone please tell me I am blind!

Cloning Snapshots in Corral?

 

[whitey]

Well isn't this just effed up? I MUST be having a slow night or losing my damned mind!

Riddle me that???

[root@freenas-2] /mnt/vdisk/nfs# zfs list
NAME USED AVAIL REFER MOUNTPOINT
freenas-boot 1.17G 18.1G 64K none
freenas-boot/.system-289f3577 56.5M 18.1G 56.5M /var/db/system
freenas-boot/ROOT 1.11G 18.1G 29K none
freenas-boot/ROOT/Initial-Install 1K 18.1G 1.11G legacy
freenas-boot/ROOT/default 1.11G 18.1G 1.11G legacy
freenas-boot/grub 4.88M 18.1G 4.88M legacy
vdisk 13.8G 80.7G 104K /mnt/vdisk
vdisk/nfs 13.8G 80.7G 13.8G /mnt/vdisk/nfs
[root@freenas-2] /mnt/vdisk/nfs# ls
./ ../ .config-nfs-nfs.json .iorm.sf/ .iormstats.sf* .lck-0e00000000000000*
[root@freenas-2] /mnt/vdisk/nfs# du -h .lck-0e00000000000000
512B .lck-0e00000000000000
[root@freenas-2] /mnt/vdisk/nfs# ll .
../ ./ .config-nfs-nfs.json .iorm.sf/ .iormstats.sf* .lck-0e00000000000000*
[root@freenas-2] /mnt/vdisk/nfs# ls -al
total 19
drwxrwxrwx 3 root wheel 6 Mar 20 22:13 ./
drwxr-xr-x 3 root wheel 3 Mar 20 21:54 ../
-rw------- 1 root wheel 512 Mar 20 22:13 .config-nfs-nfs.json
drwxr-xr-x 2 root wheel 3 Mar 20 22:12 .iorm.sf/
-rwxr-xr-x 1 root wheel 16511 Mar 20 22:12 .iormstats.sf*
-rwxrwxr-x 1 root wheel 84 Mar 20 22:12 .lck-0e00000000000000*
[root@freenas-2] /mnt/vdisk/nfs# cd .
[root@freenas-2] /mnt/vdisk/nfs# ls -al
total 19
drwxrwxrwx 3 root wheel 6 Mar 20 22:13 ./
drwxr-xr-x 3 root wheel 3 Mar 20 21:54 ../
-rw------- 1 root wheel 512 Mar 20 22:13 .config-nfs-nfs.json
drwxr-xr-x 2 root wheel 3 Mar 20 22:12 .iorm.sf/
-rwxr-xr-x 1 root wheel 16511 Mar 20 22:12 .iormstats.sf*
-rwxrwxr-x 1 root wheel 84 Mar 20 22:12 .lck-0e00000000000000*
[root@freenas-2] /mnt/vdisk/nfs# zfs clone vdisk/nfs@repl-20170321.0503 vdisk/wtf
[root@freenas-2] /mnt/vdisk/nfs# zfs list
NAME USED AVAIL REFER MOUNTPOINT
freenas-boot 1.18G 18.1G 64K none
freenas-boot/.system-289f3577 56.6M 18.1G 56.6M /var/db/system
freenas-boot/ROOT 1.11G 18.1G 29K none
freenas-boot/ROOT/Initial-Install 1K 18.1G 1.11G legacy
freenas-boot/ROOT/default 1.11G 18.1G 1.11G legacy
freenas-boot/grub 4.88M 18.1G 4.88M legacy
vdisk 13.8G 80.7G 104K /mnt/vdisk
vdisk/nfs 13.8G 80.7G 13.8G /mnt/vdisk/nfs
vdisk/wtf 0 80.7G 13.8G /mnt/vdisk/wtf
[root@freenas-2] /mnt/vdisk/nfs# cd /mnt/vdisk/wtf/
[root@freenas-2] /mnt/vdisk/wtf# ls
./ .config-nfs-nfs.json .iormstats.sf* .vSphere-HA/
../ .iorm.sf/ .lck-0c00000000000000* corral-jumpstation/
[root@freenas-2] /mnt/vdisk/wtf#

 

[whitey]

Quickly growing irritated w/ Corral lol, now I see that replication jobs seem to be coming over as read only...even though read only is not ticked/setup...even tried to pre-seed the destination dataset prior to replication kickoff (an old trick I learned in FreeNAS 9.x that if skipped would cause rep job to send as readonly)...still no luv, then I pinged a buddy of mine to peek in...couldn't get in, seems I didn't get DGW set 'somehow' when I swapped from DHCP to static IP and I CANNOT input that info from UI (red circle w/ slash through it). LOVELY, this fixed it from freenas cli

unix::/network/config>set ipv4_gateway=10.0.0.1 dns_servers=8.8.8.8

Also I CAN manually clone the snapshot that was used for replication on the dest system but again via ssh in cli 'zfs clone volume/snapshotname volume/newdatasetname' and THEN I can access data/mount to vSphere and see replicated VM/data...SMFH SRSLY!

Gimme my goshdamned 'clone' snapshot button back por favor FreeNAS team and stop w/ all this read-only nonsense unless I choose to keep a dataset read-only. AAARRRGGGHHH

WEAK SAUCE...finding bullet riddled holes all over the place. UI's a lil flaky/janky w/ updating rep jobs in real time...seems a logout and log back in resolves it but severely annoying.

 

[PigLover]

Your "quick trick" on 9.10 was actually a bug. Even their (limited) documentation clearly said that replication jobs would send read-only. Snapshot replication doesn't work reliably if you modify the target between snapshots...

That said - I do find a lot of wobbly-ness in Corral. Not sure I'm sold on the UI. It still has UI caching bugs (where you have to log out and start over to get it to show the correct state of the system). Etc...

And - for some reason - I still can't get replication to work at all. Weird. I know its probably some strange artifact due to both sides being "upgrades" instead of new-starts. But it is frustrating.

 

[whitey]

Good deal, thanks for the feedback/info, yeah I noticed the UI thing not updating on rep jobs...REALLY irritating/dejecting.

Why in the hell would they take a CORE function like cloning a snapshot out of the UI though...just doesn't make sense. That was a SUPER handy capability, guess it's still there via cli once ssh'ed in but a SMH moment for sure.

Things will inevitably get better but the release does feel a bit premature...either that or we are nit picky but I don't think we are expecting too much from a GA release :-D