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 the kernel with the ZFS port.
This may indicate if a strange filesystem level issue is causing
corruption or if the port has changed / broken a kernel feature go is
relying on.
Regards
Steve
On 19/07/2019 22:01, B Carr wrote:
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 ZFS rebased to ZFS on Linux I'm seeing issues that I can
only reproduce building Go.
--
You received this message because you are subscribed to the Google
Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to golang-nuts+unsubscr...@googlegroups.com
<mailto:golang-nuts+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/fb3ca79e-cd21-4b4f-ac6c-4e608825d26e%40googlegroups.com
<https://groups.google.com/d/msgid/golang-nuts/fb3ca79e-cd21-4b4f-ac6c-4e608825d26e%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/2dc3cd67-9bd1-8ca7-df85-2f4436ecc103%40multiplay.co.uk.
