Correct setup for zfs receive_resume_token, but no token shown in properties?

[Stilez]

I just set up a new replication server, and have been testing it.

My main server and this are both using 11.1-U5, both enterprise hardware, and all features enabled. I ran zfs send on the main server and zfs receive on the new backup server, and deliberately killed the process after a while to check resume works - but there's no resume token. I'm now worried.

command run on new backup server:
# nc -l 2000 | zfs receive -vvFsd mypool

command run on master, to back up entire pool at a new snapshot taken today:
# zfs send -vvDRLe mypool@test_snap | nc -N 192.168.0.2 2000

I let these run for an hour, then killed and tried to resume, and there's no resume token. The following properties are set on the receiving server - you can see that the creation dates for everything is today, it's the right server . I've removed some properties like compression/quota which clearly aren't relevant:

# zpool get all mypool
NAME PROPERTY VALUE SOURCE
mypool size 18.1T -
mypool capacity 4% -
mypool altroot /mnt local
mypool free 17.4T -
mypool allocated 745G -
mypool readonly off -
mypool feature@async_destroy enabled local
mypool feature@empty_bpobj active local
mypool feature@lz4_compress active local
mypool feature@multi_vdev_crash_dump enabled local
mypool feature@spacemap_histogram active local
mypool feature@enabled_txg active local
mypool feature@hole_birth active local
mypool feature@extensible_dataset active local
mypool feature@embedded_data active local
mypool feature@bookmarks enabled local
mypool feature@filesystem_limits enabled local
mypool feature@large_blocks enabled local
mypool feature@sha512 enabled local
mypool feature@skein enabled local

# zfs get all mypool
NAME PROPERTY VALUE SOURCE
mypool type filesystem -
mypool creation Mon Jun 11 10:05 2018 -
mypool used 4.55T -
mypool available 13.6T -
mypool compressratio 1.38x -
mypool mounted yes -
mypool recordsize 128K default
mypool mountpoint /mnt/mypool default
mypool checksum on default
mypool compression lz4 local
mypool readonly off default
mypool snapdir visible local
mypool version 5 -
mypool written 0 -
mypool logicalused 1.68T -
mypool logicalreferenced 12.5K -
mypool volmode default default
mypool filesystem_count none default
mypool snapshot_count none default
mypool redundant_metadata all default
mypool org.freenas:description received
mypool org.freebsd.ioc:active yes received

# zfs get all mypool@test_snap
NAME PROPERTY VALUE SOURCE
mypool@test_snap type snapshot -
mypool@test_snap creation Mon Jun 11 11:15 2018 -
mypool@test_snap used 0 -
mypool@test_snap referenced 96K -
mypool@test_snap version 5 -
mypool@test_snap written 0 -
mypool@test_snap logicalused 0 -
mypool@test_snap logicalreferenced 12.5K -
mypool@test_snap volmode default default
mypool@test_snap org.freenas:description inherited from mypool
mypool@test_snap org.freebsd.ioc:active yes inherited from mypool

The extensible_dataset feature is enabled, the command had -s .... where's my resume token?

 

[Chris Moore]

It appears that resume has not been implemented yet:
https://redmine.ixsystems.com/issues/24137

 

[Chris Moore]

Also, this was discussed a while back, perhaps you might make some noise to get attention for it:
https://forums.freenas.org/index.ph...ceive-resuming-an-interrupted-transfer.42873/

 

[Stilez]

Can you double check that? The posts you're linking to seem to be about handling resume within the GUI. Neither of them seem to suggest the functionality is fundamentally missing at CLI level and can't be accessed (or isn't set) when a receive aborts. That seems to have stopped being an issue around 9.x/10.x from those links.

The only criteria I can find are that relevant features must be enabled and -s flag provided to the zfs receive command.

But as shown above, when I interrupt the transfer, the properties at CLI level don't include a receive_resume_token at pool, dataset or snapshot levels. I just tested again.

 

[Stilez]

Update - oddly, a resume token *did* appear in properties at some point, but not at other points. I'm not sure why. It clearly works, but sometimes when I checked properties one was listed, sometimes it wasn't.