OS X 'find' nogroup/nouser doesn't traverse directories?

UNIX macOS
1 
flamingo:~ joliver$ sudo find / -nogroup
find: /dev/fd/4: No such file or directory
find: /home: No such file or directory
find: /Library: No such file or directory
find: /net: No such file or directory
find: /Network: No such file or directory
find: /private: No such file or directory
find: /sbin: No such file or directory
find: /System: No such file or directory
find: /Users: No such file or directory
find: /usr: No such file or directory
find: /Volumes: No such file or directory
flamingo:~ joliver$ ls -l /
total 30453
drwxrwxr-x+ 40 root  admin      1360 Oct 23 16:01 Applications
drwxr-xr-x+ 66 root  wheel      2244 Oct 12 15:01 Library
drwxr-xr-x@  2 root  wheel        68 Jun 18  2011 Network
drwxr-xr-x+  4 root  wheel       136 Oct  1 14:08 System
drwxr-xr-x   7 root  admin       238 Oct 12 10:19 Users
drwxrwxrwt@  4 root  admin       136 Oct 26 14:16 Volumes
drwxr-xr-x@ 39 root  wheel      1326 Oct  1 14:01 bin
drwxrwxr-t@  2 root  admin        68 Jun 18  2011 cores
dr-xr-xr-x   3 root  wheel      4250 Oct 26 13:30 dev
lrwxr-xr-x@  1 root  wheel        11 Oct  1 12:52 etc -> private/etc
dr-xr-xr-x   2 root  wheel         1 Oct 26 13:46 home
-rw-r--r--@  1 root  wheel  15572704 Aug 23 16:27 mach_kernel
dr-xr-xr-x   2 root  wheel         1 Oct 26 13:46 net
drwxr-xr-x@  6 root  wheel       204 Oct  1 12:57 private
drwxr-xr-x@ 62 root  wheel      2108 Oct  1 14:01 sbin
lrwxr-xr-x@  1 root  wheel        11 Oct  1 12:52 tmp -> private/tmp
drwxr-xr-x@ 12 root  wheel       408 Oct 15 08:22 usr
lrwxr-xr-x@  1 root  wheel        11 Oct  1 12:52 var -> private/var

Yet it can if I specify a directory:

flamingo:~ joliver$ sudo find /Library -nogroup
/Library/McAfee/abm
/Library/McAfee/abm/bin
/Library/McAfee/abm/bin/abm
/Library/McAfee/abm/lib
/Library/McAfee/abm/lib/libABMCommon-3.5.0.1.0.0.dylib
/Library/McAfee/abm/lib/libABMCommon-3.5.0.1.dylib
/Library/McAfee/abm/lib/libABMCommon.dylib
/Library/McAfee/abm/lib/libABMCommon.la
/Library/McAfee/abm/lib/libABMEngine-1.0.0.1.0.0.dylib
/Library/McAfee/abm/lib/libABMEngine-1.0.0.1.dylib
/Library/McAfee/abm/lib/libABMEngine.dylib
/Library/McAfee/abm/lib/libABMEngine.la
/Library/McAfee/abm/lib/libABMPlugin-3.5.0.1.0.0.dylib
/Library/McAfee/abm/lib/libABMPlugin-3.5.0.1.dylib
/Library/McAfee/abm/lib/libABMPlugin.dylib
/Library/McAfee/abm/lib/libABMPlugin.la
/Library/McAfee/abm/lib/libboost_date_time.dylib
/Library/McAfee/abm/lib/libboost_filesystem.dylib
/Library/McAfee/abm/lib/libboost_program_options.dylib
/Library/McAfee/abm/lib/libboost_regex.dylib
/Library/McAfee/abm/lib/libboost_system.dylib
/Library/McAfee/abm/lib/libsqlite3.0.8.6.dylib
/Library/McAfee/abm/lib/libsqlite3.0.dylib
/Library/McAfee/abm/lib/libsqlite3.dylib
/Library/McAfee/abm/lib/libsqlite3.la
2

It works under Mountain Lion (10.8.2) traversing the folders and finding items.
It appears to run successfully under Snow Leopard (10.6.8) and Lion (10.7.4) but only reports /dev/fd/3 and /dev/fd/4 are not directories.
The 10.6 and 10.7 find only returned those results, nothing else.

What OS version are you using the command on?
Possible permissions repair issue?

3

Lion 10.7.5

I've done the repairPermissions thing several times, and there are a bunch of items that it still complains about. I haven't had any call yet to try to figure out what it's comparing permissions against to determine what's "right" and what's "wrong".

---------- Post updated 10-30-12 at 03:26 PM ---------- Previous update was 10-29-12 at 04:09 PM ----------

I'm getting this more and more frequently. It isn't just with -nogroup and -nouser... it happens apparently with any find starting in / and it seems to start happening after I've been fiddling around with finds. At first, I wondered if there was an issue with the fact I was using PuTTY from a Windows machine, especially as a few times I closed a session, opened a new one, and this behavior went away, at least for a while. But it started happening again, and it persists even in a terminal on the Mac. And closing sessions isn't helping. I'm guessing some sort of environmental pollution?

For giggles, I cd'ed to / and ran a find from . and it works, while a find from / fails. So I guess I have a workaround.