Warning: Hard Link Count Is Wrong For /: This May Be A Bug In Your Fil

Whenever I use the FIND command I get this error:

find: WARNING: Hard link count is wrong for /: this may be a bug in your filesystem driver. Automatically turning on find's -noleaf option. Earlier results may have failed to include directories that should have been searched.[/b]

Im using Suse 10.1, Kernel Version: 2.6.16.13-4-smp (I recompliled recently to the SMP version I was using the default, and I still got this error, as I just recently upgraded to a 64 x2, but I was still getting this error with the original kernel/cpu)

I noticed similar errors around but it was for the /proc and mine isnt give me that error just the /:

Any suggestions besides using the "Locate" Command.

Whenever I use the FIND command I get this error:
Im using Suse 10.1, Kernel Version: 2.6.16.13-4-smp (I recompliled recently to the SMP version I was using the default, and I still got this error, as I just recently upgraded to a 64 x2, but I was still getting this error with the original kernel/cpu)

I noticed similar errors around but it was for the /proc and mine isnt give me that error just the /:

Any suggestions besides using the "Locate" Command.
[/b]

find gets confused by the pseudo-filesystems /proc /sys /subdomain etc. Don't run find starting from /.

Not to sound ignorant but if i dont use "find / -name xxx" then it wont search all directories am I correct?" what is another alternative?

Not to sound ignorant but if i dont use "find / -name xxx" then it wont search all directories am I correct?" what is another alternative?
[/b]

find /etc /usr /home /lib /opt ... -name xxx

Those are the most likely places for what you want anyway. Make an alias of it if you do it often. Anyway it's an inefficient way to do it, which is why we have locate and beagle.

Or live with the bogus error message.

find /etc /usr /home /lib /opt ... -name xxx

Those are the most likely places for what you want anyway. Make an alias of it if you do it often. Anyway it's an inefficient way to do it, which is why we have locate and beagle.

Or live with the bogus error message.
[/b]

I agree and thanks for the fast response!