JMoVS

@ahrens how many can be done in one txg? Because my system had to delete 1000 per dataset right now, so I‘m not sure if zfs would handle that :D

it is used as from and it might also simply be not accessible and offline by the time. Now is it possible to resume a resumable send from a bookmark?

Hmm ok, if resuming a send from a bookmark works, then your strategy of creating a bookmark for every hold and then releasing that hold, enabling the pruner to delete...

zrepl currently holds like 200 snapshots per dataset for me currently. So this might also be a separate bug. But yes, you understood correctly, I effectively want to make an...

yes, that would work I think. As long as at all times there will be a bookmark to increment from. ;-)

so the `guid` links snapshot to bookmark? > > so my source showed: > > ``` > > #zrepl_replication_cursor > > @snapshotNewer > > ``` > > > > >...

the problem is that if I remember correctly, it just printed the #zrepl_replication_cursor as latest available, but didn't show which one was the corresponding snapshot. So figuring out the #zrepl_replication_curossnapshot...

Example: ``` ocean/Users/justin/Cloudy PLANNING-ERROR (step 0/0, 0 B/0 B) the receiver's latest snapshot is not present on sender: last common: #zrepl_replication_cursor sender-only: @zrepl_20190714_082143_000 @zrepl_20190714_082908_000 @zrepl_20190714_083925_000 @zrepl_20190714_084930_000 @zrepl_20190714_090421_000 @zrepl_20190714_091457_000 @zrepl_20190714_092403_000 @zrepl_20190714_093356_000...

actually also applies for message arrival sounds

@rottegift I am currently unsure why gthe package that lundman provided doesn't work but if it's easy for you to test the latest commit, I would greatly appreciate your help...