SOLVED Copy of Jail Dataset broken?

[maglin]

First my issue. I have a test Raidz1 setup from when I first started testing FreeNAS 9.3. I have upgraded FreeNAS to 9.10 and re verified the files through the GUI. I deleted all jails after the upgrade and created a new jail running all my media stuffs which took several days to get working correctly. Now I want to move that jail dataset to another pool so I can destroy the test Pool and rebuild it with Stripped Mirrors after which I want to move the jail dataset onto the newly built pool.

I was trying to use https://forums.freenas.org/index.php?threads/copy-move-dataset.28876/ and I kept getting some origin error. So I tried moving a new dataset with a 1GB file it in and it worked with no problems. I think I've narrowed it down to the actual jail template causing the problem. Here is what I'm seeing.

Code:

[maglin@freenas] /nonexistent# zfs send -Rv Test/temp@copy | zfs receive -Fv Test/copy
full send of Test/temp@copy estimated size is 5.46M
total estimated size is 5.46M
TIME        SENT   SNAPSHOT
found clone origin Test/.warden-template-standard@clean
receiving incremental stream of Test/temp@copy into Test/copy@copy
cannot receive new filesystem stream: invalid backup stream
warning: cannot send 'Test/temp@copy': signal received

That was on a brand new empty jail that I created for testing. I have destroyed those datasets now reflected in the zfs list below. I don't know how to fix this. I would like to be able to just re-download the jail template and see if that will fix it. Any help is appreacted. My system specs:
FreeNAS 9.10 - Stable
MB: X10SLL+-F-O
CPU: Xeon E3-1231 v3
RAM: Crucial 32GB ECC
POOLs: 3x8TB Seagates in RAIDz1 : 3x1TB WD in RAIDz1 w/ 1x1TB WD not attached to a pool

(I know about RAIDz1 and am going to rebuild into a RAIDz2 when I have 6 Disks and enough temp storage to do so, but it's just Media files that ultimately won't hurt me to loose (just would rather not))

And if needed my zfs list

Code:

[maglin@freenas] /nonexistent# zfs list
NAME                                                         USED  AVAIL  REFER  MOUNTPOINT
Storage                                                     10.4T  3.67T   128K  /mnt/Storage
Storage/CIFS                                                 814G  3.67T   814G  /mnt/Storage/CIFS
Storage/Storage                                             9.57T  3.67T  9.57T  /mnt/Storage/Storage
Test                                                        18.2G  1.74T   160K  /mnt/Test
Test/.system                                                20.3M  1.74T   139K  legacy
Test/.system/configs-f1ae6c68bbe041c7bb38cadeec088781       6.08M  1.74T  6.08M  legacy
Test/.system/cores                                          5.39M  1.74T  5.39M  legacy
Test/.system/rrd-f1ae6c68bbe041c7bb38cadeec088781            128K  1.74T   128K  legacy
Test/.system/samba4                                          618K  1.74T   618K  legacy
Test/.system/syslog-f1ae6c68bbe041c7bb38cadeec088781        8.02M  1.74T  8.02M  legacy
Test/.warden-template-VirtualBox-4.3.12                      727M  1.74T   727M  /mnt/Test/.warden-template-VirtualBox-4.3.12
Test/.warden-template-pluginjail                             519M  1.74T   519M  /mnt/Test/.warden-template-pluginjail
Test/.warden-template-standard                              2.02G  1.74T  1.94G  /mnt/Test/.warden-template-standard
Test/jail                                                   2.15M  1.74T  2.15M  /mnt/Test/jail
Test/media_jail                                             14.8G  1.74T  15.9G  /mnt/Test/media_jail
freenas-boot                                                1.84G  12.6G    31K  none
freenas-boot/ROOT                                           1.80G  12.6G    25K  none
freenas-boot/ROOT/9.10-STABLE-201603252134                  1.77G  12.6G   502M  /
freenas-boot/ROOT/FreeNAS-9.3-STABLE-201509160044           7.44M  12.6G   518M  /
freenas-boot/ROOT/FreeNAS-9.3-STABLE-201509282017           2.01M  12.6G   513M  /
freenas-boot/ROOT/FreeNAS-d1851bb004ead848f18f828f8fd48bae  6.27M  12.6G   475M  /
freenas-boot/ROOT/Initial-Install                              1K  12.6G   508M  legacy
freenas-boot/ROOT/Wizard-2015-07-08_17:08:25                   1K  12.6G   508M  legacy
freenas-boot/ROOT/Wizard-2015-07-08_17:36:46                   1K  12.6G   508M  legacy
freenas-boot/ROOT/Wizard-2015-07-08_17:43:26                   1K  12.6G   508M  legacy
freenas-boot/ROOT/Wizard-2015-07-08_18:31:06                   1K  12.6G   509M  legacy
freenas-boot/ROOT/Wizard-2015-08-09_14:16:44                   1K  12.6G   508M  legacy
freenas-boot/ROOT/Wizard-2015-08-10_07:06:27                   1K  12.6G   509M  legacy
freenas-boot/ROOT/Wizard-2016-03-27_14:35:16                   1K  12.6G   498M  /
freenas-boot/ROOT/Wizard-2016-03-27_14:40:53                   1K  12.6G   498M  /
freenas-boot/ROOT/default                                   7.94M  12.6G   516M  legacy
freenas-boot/grub                                           33.1M  12.6G  6.33M  legacy

I would really hate to reinstall FreeNAS but I if have to go that route I will as well. I just did the upgrade because I had FreeNAS working correctly. In hind sight I should have done a Fresh install of FreeNAS with 9.10.

Edit: So my issue was due to the jail template physically being located on a different dataset. When I moved the entire pool as a dataset it worked as expected. Also my system dataset was located on that same pool I was wanting to destroy. So I had to move the pointer to it was well in system-system Dataset. I was able to move everything and rebuild the pool as a stripped mirror. The bonus is now my jails run a good deal faster.

 

[Sakuru]

Fist my issue

No thanks, I don't know you ;)

Try removing the -Fv from zfs receive. -F should not be necessary because Test/copy does not exist.

 

[maglin]

No thanks, I don't know you ;)

Try removing the -Fv from zfs receive. -F should not be necessary because Test/copy does not exist.

I always seem to screw up posting. I reread my posts and I sound like a 5th grader. The Test/copy and Test/temp datasets I created for testing and I've destroyed them before that zfs list I posted. You can see my Test/media_jail which is the dataset I want to copy. I wanted to see if I created a brand new jail and attempted to send | receive it if it would work and it doesn't. I guess if I have to I'll just kept my jail on the RAIDz1 but I really want it on a stripped mirror as I have the drives for it. What I don't want to do is rebuild that jail. I thought about using rsync but that wants to copy my mounts which has over 10TB of data on it.

I don't think there is a way to remove the FreeBSD jail template without killing my current jail. That seems to be what is broken or at least not working correctly. Others where able to use these commands on there jails in 9.3. I can google and read and usually figure these things out. This appears to not be one of those times.

 

[maglin]

So I finally figured out what my problem was. I had my jail config pointing to Test dataset/pool and my jail I was attempting to move was in Test/media_jail. So my templates for the jail was in Test and trying to move Test/media_jail failed because the image it was using was up a level. So I moved the entire Test dataset/pool to my other pool Storage/temp for the move and it started to copy. This also showed me a few things left over from my testing when I was on FreeNAS 9.3 that I'm going to clean up specifically old plugin templates and Vbox template. I just didn't understand the origin errors. Now I understand them. I'll report back when all is finished and working.