Cannot finish initial sync for nested datasets

[Peter2121]

zstorage-1# zrep -i zdata/NFSROOT zstorage-2 zdata/NFSROOT
Setting zrep properties on zdata/NFSROOT
Warning: zfs recv lacking -o readonly
Creating destination filesystem as separate step
Creating snapshot zdata/NFSROOT@zrep_000000
Sending initial replication stream to zstorage-2:zdata/NFSROOT
cannot mount 'zdata/NFSROOT': mountpoint or dataset is busy
Destroying any zrep-related snapshots from zdata/NFSROOT
Removing zrep-related properties from zdata/NFSROOT
Error: Error transferring zdata/NFSROOT@zrep_000000 to zstorage-2:zdata/NFSROOT. Resetting

On source side:

zstorage-1# zfs list | grep zdata
zdata                             141G  52.1G    23K  /zdata
zdata/NFSROOT                     141G  52.1G    23K  /NFSROOT
zdata/NFSROOT/GLE-data            141G  52.1G    23K  /NFSROOT/GLE-data
zdata/NFSROOT/GLE-data/bimp       141G  52.1G   140G  /NFSROOT/GLE-data/bimp

On destination side:

zstorage-2# zrep -l
zstorage-2# zfs list | grep zdata
zdata                             110G   161G    23K  none
zdata/NFSROOT.bkp                 110G   161G    23K  /NFSROOT.bkp
zdata/NFSROOT.bkp/GLE-data        110G   161G    23K  /NFSROOT.bkp/GLE-data
zdata/NFSROOT.bkp/GLE-data/bimp   110G   161G   109G  /NFSROOT.bkp/GLE-data/bimp

Root folder for the destination mount is created:

zstorage-2# ls -lisa / | grep NFS
131661 1 drwxr-xr-x   2 root  wheel     2 Dec 23 17:40 NFSROOT
     4 1 drwxr-xr-x   3 root  wheel     3 Oct 22 17:40 NFSROOT.bkp

I don't understand the reason of the fail, but maybe it is related to the old synced dataset on destination side, renamed to zdata/NFSROOT.bkp which I would prefer to leave here (the sync was broken and I could not continue it correctly). The old dataset was cleaned with zrep clean and renamed.

Even if there is an error somewhere in options or mounts, it is not really cool to delete everything after several hours of initial transfer. I tried twice with the same error :(

[ppbrown]

yeah... Im not happy with the way things work.... but zrep depends on ZFS. and recursive syncs with ZFS are.... tricky. I always recommend that people do syncs individually, not recursive, whenever possible. Which should be fine in almost all cases, since you can run multiple zreps in parallel. If you do them one at a time, you can also do the -r option, which is for "resume" a partial send.

…

On Wed, Dec 23, 2020 at 9:49 AM Пётр ***@***.***> wrote: zstorage-1# zrep -i zdata/NFSROOT zstorage-2 zdata/NFSROOT Setting zrep properties on zdata/NFSROOT Warning: zfs recv lacking -o readonly Creating destination filesystem as separate step Creating snapshot ***@***.***_000000 Sending initial replication stream to zstorage-2:zdata/NFSROOT cannot mount 'zdata/NFSROOT': mountpoint or dataset is busy Destroying any zrep-related snapshots from zdata/NFSROOT Removing zrep-related properties from zdata/NFSROOT Error: Error transferring ***@***.***_000000 to zstorage-2:zdata/NFSROOT. Resetting On source side: zstorage-1# zfs list | grep zdata zdata 141G 52.1G 23K /zdata zdata/NFSROOT 141G 52.1G 23K /NFSROOT zdata/NFSROOT/GLE-data 141G 52.1G 23K /NFSROOT/GLE-data zdata/NFSROOT/GLE-data/bimp 141G 52.1G 140G /NFSROOT/GLE-data/bimp On destination side: zstorage-2# zrep -l zstorage-2# zfs list | grep zdata zdata 110G 161G 23K none zdata/NFSROOT.bkp 110G 161G 23K /NFSROOT.bkp zdata/NFSROOT.bkp/GLE-data 110G 161G 23K /NFSROOT.bkp/GLE-data zdata/NFSROOT.bkp/GLE-data/bimp 110G 161G 109G /NFSROOT.bkp/GLE-data/bimp Root folder for the destination mount is created: zstorage-2# ls -lisa / | grep NFS 131661 1 drwxr-xr-x 2 root wheel 2 Dec 23 17:40 NFSROOT 4 1 drwxr-xr-x 3 root wheel 3 Oct 22 17:40 NFSROOT.bkp I don't understand the reason of the fail, but maybe it is related to the old synced dataset on destination side, renamed to zdata/NFSROOT.bkp which I would prefer to leave here (the sync was broken and I could not continue it correctly). The old dataset was cleaned with zrep clean and renamed. Even if there is an error somewhere in options or mounts, it is not really cool to delete everything after several hours of initial transfer. I tried twice with the same error :( — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#165>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANEV6LXQHNASPUJSXQ7YOLSWIUULANCNFSM4VHIM6DQ> .