You might want to see if dtrace can shed some light on this?
On Sat, 20 Jul 2019 at 01:25, wrote:
>
>
> On Friday, July 19, 2019 at 2:24:30 PM UTC-7, Steven Hartland wrote:
>>
>> Mat is actually running a non-standard kernel, with the ZFS filesystem
>> from the core OS replaced with a ZFS versio
On Friday, July 19, 2019 at 2:24:30 PM UTC-7, Steven Hartland wrote:
>
> Mat is actually running a non-standard kernel, with the ZFS filesystem
> from the core OS replaced with a ZFS version derived from Linux ZFS port.
>
> I've not looked at the details of the port, but one suggestion would be
Mat is actually running a non-standard kernel, with the ZFS filesystem
from the core OS replaced with a ZFS version derived from Linux ZFS port.
I've not looked at the details of the port, but one suggestion would be
do you see the same behaviour if you build on UFS volume while still
running
What does this part mean? "...with the ZFS rebased to ZFS on Linux..."
On Friday, July 19, 2019 at 1:37:02 PM UTC-6, mat...@gmail.com wrote:
>
> I'm not sure where to ask this since this isn't actually a Go bug. Go
> 1.12, 1.1, etc build fine on FreeBSD with ZFS in base. However, with the
> ZF
