replications of zvol fails
Description
Problem/Justification
Impact
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
Peter Boos April 12, 2021 at 9:20 AM
Created a new unencrypted pool added dataset Zvol, in it i made a Zvol.
Adjusted replication and its running, it will take some time, i'll let you now if it succeeds.
--------------------------------------------------------------------------
PS from a usability standpoint some feedback towards the developers.
This should be made more clear, it will reduce the cases and reported problems.
There could be added validation checks when one creates a config that is not supported. With some human readable text explaining why not, and maybe suggestions for alternative configuration, just spend a html page on, as pages are not so expensive this days.
Another solution by developers would be to just support this kind of replication (including recursive).
There might be problem currently but anything defined in code is solvable in code.Dirty workaround solutions like making recursive grayed out, if the dataset contains a Zvol is possible as well. alter the popup as well to explain that. Or a human readable red error text explaining it.
Vladimir Vinogradenko April 9, 2021 at 3:19 PM
@unknown you'll have to destroy the target dataset. Currently we do not support replicating from scratch onto an existing encrypted volume.
Peter Boos April 9, 2021 at 12:41 PM
Well isnt that the main problem why i raised this call... that we dont get the zvol replicated ?
Replication of Zvol fails and so also the snapshots from freenas dont get over by Pull to truenas
There are no snapshots on the treunas system
Vladimir Vinogradenko April 9, 2021 at 12:23 PM
@unknown it matches.
However, all of your screenshots show that there are snapshots on pool1/production/iscsi_vm_root
None of them shows which snapshots are there on pool2/iscsi_vmroot_backup
Truenas replication task error.
Replication "pool1\xxxx\ISCI_vm_root backup" failed: Source 'pool1\xxxx\IS_vm_root' is a volume, but target 'pool3' already exists and is a filesystem.
Essentially we got a nested secure storagepools structure
Somewhere deep there is a large ZVOL we would like to pull over.
Each secure pool has its own replciation schedule
Its not possible to select the ZVOL (although its selecteable), and to set a target system
The replication simply fails, all i want is this zvol to replicate there as a zvol (large chink from A to B, zvol has its own inner file system, so this shouldnt matter what ever the target pool contains.