The statfs implementation in sys/compat/linux/linux_stats.c (function bsd_to_linux_ftype) does not currently handle zfs filesystems. Some proprietary software (e.g. Splunk) expects a sane value for statfs.f_type and will refuse to function when that's 0L. SmartOS solved this issue (https://smartos.org/bugview/OS-3932) by presenting zfs as ext2; the same solution should work for FreeBSD.
What value does ZFS on Linux present?
FWIW, a Linux user reports ZFS on Linux shows 2fc12fc1 for statfs f_type. I don't think pretending to be ext2 makes much sense.
Can you try the patch in https://reviews.freebsd.org/D11252
A commit references this bug: Author: emaste Date: Sun Jun 18 11:51:04 UTC 2017 New revision: 320069 URL: https://svnweb.freebsd.org/changeset/base/320069 Log: Add ZFS to Linux statfs ftype PR: 220086 Reviewed by: cem MFC after: 3 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D11252 Changes: head/sys/compat/linux/linux_stats.c
A commit references this bug: Author: emaste Date: Sun Jul 9 00:24:52 UTC 2017 New revision: 320821 URL: https://svnweb.freebsd.org/changeset/base/320821 Log: MFC r320069: Add ZFS to Linux statfs ftype PR: 220086 Sponsored by: The FreeBSD Foundation Changes: _U stable/11/ stable/11/sys/compat/linux/linux_stats.c
A commit references this bug: Author: emaste Date: Sat Sep 9 14:30:17 UTC 2017 New revision: 323366 URL: https://svnweb.freebsd.org/changeset/base/323366 Log: MFC r320069: Add ZFS to Linux statfs ftype PR: 220086 Approved by: re (gjb) Sponsored by: The FreeBSD Foundation Changes: _U stable/10/ stable/10/sys/compat/linux/linux_stats.c
batch change: For bugs that match the following - Status Is In progress AND - Untouched since 2018-01-01. AND - Affects Base System OR Documentation DO: Reset to open status. Note: I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Thank you for the bug report - fix committed to HEAD and merged to stable/11 and stable/10. If this issue persists please reopen this PR.