Replication job started failing

[Kyryl]

Hi!

I have two nodes configured, with the container on one of the nodes with additional volume mounted (configured with 1M record size). Replication used to run OK between node1 and node2, as well as migration to the the node2, but now incremental replication task started failing with:

... cannot receive incremental stream: incremental send stream requires -L (--large-block), to match previous receive. ...

I have another container with the 1M record size setup (initially running at node1) exhibiting the same issue and I was managed to work around the issue by completely deleting the volume on the 'destination' node (node1) and doing full replication once - after that I was able to migrate the container to the node1 but now the replication node1 -> node2 for that container started having the same issue. I guess removing the volume on node2 and doing full replication once would solve this issue (but keeping it in the current state to be able to investigate).

The only change that comes to mind is recent upgrade to the latest PVE (apparently pulling in the 2.0 ZFS libs).

PVE version:
#pveversion pve-manager/6.3-4/0a38c56f (running kernel: 5.4.98-1-pve)

Previously both nodes were running on the "pve-kernel-5.4.78-2-pve".

Thanks.

 

[Stoiko Ivanov]

quickly skimming through the ZFS commit logs - it seems that the error-message and handling got introduced rather recently:
https://github.com/openzfs/zfs/commit/7bcb7f0840d1857370dd1f9ee0ad48f9b7939dfd
(meaning they are in ZFS >= 2.0.0 but not in the 0.8.x series (which was shipped with pve-kernel < 5.4.98)

as described in the commit-message - this exit is there to prevent a bug with receiving snapshots without '-L', when there was a previous send with '-L'.

Did you ever send+recv (using -L) this dataset manually? (AFAICT PVE's code does not use the '-L' option for zfs send+recv )

As far as I understand the commit message removing the destination and running a complete send+recv w/o -L should be ok (also for the future)

I hope this helps!

 

[Kyryl]

Thank you for looking into it, Stoiko! To answer your question - I was not using the custom send+recv, always using the PVE replication (via web UI).

Removing the destination and doing a full send+recv does not seem to help reliably: the next time I attempt to do the send+recv in the opposite direction the issue happens again.

I've managed to reproduce it on the freshly created container with the following steps:

1. create container on node1 with specifying the root volume to be on the storage with 1M record size

2. setup replication to node2 in the container "replication" submenu, trigger replication manually couple of times (succeeds all the time - both first-time full one and incremental ones subsequently)

3. migrate container to node2 (incremental send+recv succeeds, migration succeeds as well)

4. trigger the replication to node1 in the container "replication" submenu: incremental replication starts failing immediately, with the same message

 

[fenbytech]

This issue still seems to be around, and is apparently just that PVE does not support large blocks. I can replicate it using Kyryl's steps.

Is there any reason -L can't be specified in the send every time? From the manpage:

This flag has no effect if the large_blocks pool feature is disabled, or if the recordsize property of this filesystem has
never been set above 128KB

Edit: Modifying /usr/share/perl5/PVE/Storage/ZFSPoolPlugin.pm to add the -L flag to sub volume_export gets replication/migration working again. I'm not seeing any potential side effects, either, given that the flag does nothing unless large_blocks are in use.

 

[fenbytech]

Opened a ticket on Bugzilla: https://bugzilla.proxmox.com/show_bug.cgi?id=4603

 

[ikus060]

Any update on this issue ?

I just upgraded from v7 to v8 and I'm facing this issue when trying to migrate my VM back to the server.