zfs send/recv (source proxmox) not working

[nils-trustnode]

System information

Type	Version/Name
Distribution Name	Proxmox
Distribution Version	8.2.2
Kernel Version	6.8.4-2-pve
Architecture
OpenZFS Version	zfs-2.2.3

Describe the problem you're observing

Transfering a zvol with zfs send/recv from a linux host is not working at all.

push from linux terminates with message "cannot receive new filesystem stream: I/O error"
pull from windows (cmd) terminates with message "cannot receive new filesystem stream: checksum mismatch"

Describe how to reproduce the problem

push from linux: zfs send rpool/repl/data | ssh [email protected] zfs recv -v tank/data
pull from windows: ssh [email protected] zfs send rpool/repl/data | zfs recv tank/data

[guenther-alka]

seems the same problem that I have seen when using netcat instead ssh for network replication.

[lundman]

b0f716a

[lundman]

There is a question whether zfs send (ZwWriteFile) also needs to handle short-writes.

[sskras]

ping @nils-trustnode: is your issue fixed by chance?

[nils-trustnode]

@sskras What do you mean by that? I'm waiting for the next release candidate containing the commit. I don't compile myself yet - then I'll give it a try.

[sskras]

Ah, I missed that new RC hasn't been released since the commit.

On the other hand, you could get a temporary build:

• click the CI icon (red cross) for that commit
• follow to the "windows-build-test" item
• copy the "Details" URL

This will get you this string:
https://github.com/openzfsonwindows/openzfs/actions/runs/9690271674/job/26739816856

If you trim the /job/... part & follow to bottom of the page, you will find the CI artifacts section:
https://github.com/openzfsonwindows/openzfs/actions/runs/9690271674/#artifacts

It contains link to dev_build_inno development archive:

... which includes the installer corresponding to that commit:

HTH

[lundman]

oh right, i can make one for just the send fix if you want to try it - pretty deep in debugging the mount stuff still

[lundman]

OK so surfaced. Whats the status here?