I'm testing on two Mac OS X Sierra machines (one is 10.12.5, the other is 10.12.6)
OS Version s.fs.files s.fs.mount_point File System s.fs.device_name
OS X 10.12.15 4,294,967,279 / HFS+ Journaled /dev/disk0s2
OS X 10.12.15 4,294,967,279 /Volumes/<volume2> HFS+ Journaled /dev/disk1s2
OS X 10.12.15 4,294,967,279 /Volumes/<volume1> HFS+ Journaled /dev/disk2s2
OS X 10.12.15 652 /dev n/a devfs
OS X 10.12.15 0 /net n/a map -hosts
OS X 10.12.15 0 /home n/a map auto_home
OS X 10.12.16 4,294,967,279 /Volumes/Recovery Apple_Boot /dev/disk0s3
OS X 10.12.16 4,294,967,279 / HFS+ Journaled /dev/disk1
OS X 10.12.16 4,294,967,279 /Volumes/<volume3> HFS+ Journaled /dev/disk2s2
OS X 10.12.16 4,294,967,279 /Volumes/Time Machine HFS+ /dev/disk3s2
OS X 10.12.16 1,205,990,864 /Volumes/<volume4> NTFS /dev/disk4s1
OS X 10.12.16 702 /dev n/a devfs
OS X 10.12.16 0 /net n/a map -hosts
OS X 10.12.16 0 /home n/a map auto_home
OS X 10.12.16 1,465,014,458 /Volumes/<volume5> OSX 10.6.8’s Extended Journaled via AFP //<user>@<server>._afpovertcp._tcp.local/<volume5>
So, yea, looks like HFS+ is the one that is consistently broken.
Now that I actually make a table of the data, I see a couple other 'things'...
The primary drives on the Mac machines are mounted at /, true. But they do have names that are visible through diskutil list or through an ls /Volumes, so there must be some way to pull the actual name.
Mount points that aren't actually under the /dev/disk* name space or under a /Volumes/ mount point are showing up. I can't think of a case where I'd want to have /dev show up in file system statistics. (And fwiw the /dev entry that claims 702 "files" actually has exactly half that many entries in an ls /dev