Bug 253553 - sysutils/lsof: no zfs support on 13
Summary: sysutils/lsof: no zfs support on 13
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Larry Rosenman
Depends on:
Reported: 2021-02-16 10:24 UTC by Mathieu Arnold
Modified: 2021-06-26 08:59 UTC (History)
9 users (show)

See Also:
bugzilla: maintainer-feedback? (ler)


Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu Arnold freebsd_committer 2021-02-16 10:24:43 UTC
I upgraded our package builder machine to 13.0-BETA2 to prepare our first 13.0 deployments, and when I tried to look at something, I got this:

# lsof -p 43535
lsof: WARNING: no ZFS support has been defined.
      See 00FAQ for more information.
find    43535 root    0u  VCHR  0,181 0t3109790  181 /dev/pts/2
find    43535 root    1u  VCHR  0,181 0t3109790  181 /dev/pts/2
find    43535 root    2u  VCHR  0,181 0t3109790  181 /dev/pts/2
find    43535 root    3r                             unknown file system type: zfs
find    43535 root    4r                             unknown file system type: zfs
find    43535 root    5r                             unknown file system type: zfs

I had a look at 00FAQ, but it is way beyond me.
Comment 1 Raivo Hool 2021-03-03 22:36:23 UTC
Lsof looks for zfs_znode.h to determine whether to build ZFS support. Said file has moved from the contrib/opensolaris directory to contrib/openzfs etc., and since #include paths are hard coded in Configure, it doesn't get picked up, and the support isn't included. I tried playing around with it a bit today, but encountered include escalation and put it on hold. Include paths are set in the Makefile, but there are too many files in different subdirectories with identical names that get referenced that it was not immediately apparent which need to be included and which do not.
Comment 2 ggulchin 2021-05-01 06:11:31 UTC
And progress on this? 
thanks in advance
Comment 3 Matthias Andree freebsd_committer 2021-05-18 20:16:57 UTC
Also, I would propose to install 00FAQ as a documentation file.
Comment 4 Graham Perrin 2021-06-03 16:03:48 UTC
Workaround, thanks to covacat at 

sh -c "ps ax -o pid= | xargs procstat -f 2>/dev/null"