How the heck did this ever make it through? I don't think this ever would have happened pre-OpenZFS, and undermines the stable reputation of ZFS. OpenZFS needs to do better and look to FreeBSD developers, not Linux developers, as role models.
Because it was introduced by a FreeBSD developer, and FreeBSD's fs and cp are a generation behind Linux's so they weren't even able to hit this.
>I don't think this ever would have happened pre-OpenZFS, and undermines the stable reputation of ZFS.
Of course it happened pre-OpenZFS: https://blog.lastinfirstout.net/2010/04/bit-by-bug-data-loss...
From the people that brought you Slowlaris.
>OpenZFS needs to do better and look to FreeBSD developers, not Linux developers, as role models.
This was introduced by a FreeBSD developer and was caught by a Linux one. You need to rethink your role models.
This is often regarded as a good thing in the BSD world. In all fairness, this bug just enforces that notion.
And Solaris (at least on amd64) wasn't slow. It was demanding, and not really suited for desktop. And it was picky with hardware.
Totally agree on the rest of your comment, though.
Same in Linux, which is why you'd choose a distro that's less bleeding edge.
>And Solaris (at least on amd64) wasn't slow.
No, it was slow. There's a reason why everyone in HPC/HFT/etc. moved off Solaris to Linux in the 2000s. Linux was regularly beating Slowlaris in practically every category at the end.
Honestly, this feature could have used more testing on both platforms.
Also, FreeBSD's VFS in theoretically able to support reflinks across datasets while Linux's VFS disallows that. It is not really behind.
I don't believe so, you're still not able to hardlink across file systems in BSD.
>It is not really behind.
It is behind: https://github.com/openzfs/zfs/issues/405
This hit Linux first, which is why Linux experienced the issue. FreeBSD does not currently have reflink cp.
Edit: yep, it's an older bug. Set zfs_dmu_offset_next_sync=0 to save your data
https://github.com/openzfs/zfs/issues/15526#issuecomment-182...
https://github.com/openzfs/zfs/issues/15526#issuecomment-182...
https://github.com/openzfs/zfs/pull/15571/files?diff=split&w...
https://github.com/freebsd/freebsd-src/commit/068913e4ba3dd9...
I have multiple zpools and none of them have been upgraded to enable any of these new features in the past couple years.
That said, I suspect you did not read the replies, since the code in question was written by a FreeBSD developer. Bugs in new code have been introduced by developers on both platforms. Unfortunately, the bugs in this feature were not caught before they reached a stable release. :/
I just learned the recent FreeBSD 14 release doesn't have 802.11n WiFi support. Is that considered bike shedding?