hi all, standard distro, GENERIC affected systems: 13.2-RELEASE-p8, 14.0-RELEASE-p3 affected rust: 1.75, nightly How to repeat: # cargo install pijul --version "~1.0.0-beta" # pijul -V pijul 1.0.0-beta.8 # pijul clone https://nest.pijul.com/pijul/pijul pijul Repository created at /pijul/data/pijul Downloading changes [====> ] 80/990 Applying [==> ] 52/990 Error: No error: 0 (os error 0) Research: 0. pijul clones under UFS (!) 1. pijul clones on COW FS under Linux - btrfs, bcachefs, zfs (2.0.6)
dependencies: pkg install libsodium xxhash pkgcon
I'm sorry, but I don't see what is actionable here. What output is expected?
Clone must finish successfully like on ufs mountpoint on freebsd.
^Triage: note feedback received.
Correct package is pkgconf. Thank you.
This isn't a FreeBSD base system bug, at least not without more debugging. There is an official pijul package available - have you tested that? Do you get the same result?
Right, of course, install pijul from ports. Failed the same way. How can you explain these error since UFS is ok?
(In reply to Mike from comment #7) Well, clearly there is a bug in pijul, since it says "No error" but exits anyway. If I run the example under truss, I see: posix_fallocate(0xb,0x0,0x300000) ERR#22 'Invalid argument' and indeed, ZFS does not implement fallocate on FreeBSD. There is a Linux implementation, but FreeBSD has ".vop_allocate = VOP_EINVAL". Assuming that this is the root cause of the problem, either pijul needs to tolerate such errors from posix_fallocate() if possible, or OpenZFS needs to implement fallocate on FreeBSD. cc'ed the devel/pijul maintainer in the hopes that this can be worked around somehow. :)
https://nest.pijul.com/pijul/pijul/discussions/865
btw https://github.com/openzfs/zfs/pull/13958