Problem with the #find command

jbuckley2004 · 08-23-2005, 04:24 PM

Since I first installed Mandriva 2005 LE, I've had this little warning come up whenever I use the find command as root, starting from the root directory:

find: WARNING: Hard link count is wrong for ./proc: 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.

There are only two links in the /proc directory, one of which is mounts.

Can anyone tell me how I might address this (and um... what it *means*)???
Thanks

flower.Hercules · 08-23-2005, 05:51 PM

I think this would be a bug with Mandriva.

Try running fsck, but I doubt it will help. Report it as a bug if it doesn't.

http://mandrake.vmlinuz.ca/bin/view/Main/BugReporting

jbuckley2004 · 08-24-2005, 08:04 AM

Thanks for the suggestion and link, Herc.
fsck has me a little spooked, though. The first thing it tells me is that running fsck on a mounted filesystem can cause severe damage.
Oh boy!
I'll investigate before I pull this trigger.

addy86 · 08-24-2005, 09:30 AM

Have a look at:
http://lists.debian.org/debian-user/.../msg04340.html

jbuckley2004 · 08-24-2005, 07:50 PM

Addy86 -
Thanks. You hit on it exactly (and cliearly, I"m not alone with this little bug). It's time to report it.
J

txtedmacs · 08-26-2005, 02:16 PM

Quote:

Originally posted by jbuckley2004
Addy86 -
... (and cliearly, I"m not alone with this little bug). It's time to report it.
J

Earlier, I requested advice on how to see two error messages that swept past too quickly for me to read that involved the same find command type errors. I am running Debian testing and unstable using 2.6.8 kernel (I think it's "-2"). Here is the message I get trying to run the command as su:

Quote:

find: WARNING: Hard link count is wrong for /proc/1/task: 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.

I had planned to report this too, however, I am much happier to learn I was not alone. Moreover, I had the sneaking worry I had somehow screwed up my configuration to have given myself this problem. So for once, I am not quite as big a screwup as I thought. Nonetheless, I have other problems that I will either solve or that I will finally ask for solutions here when my efforts fail. THANKS!

player_2 · 08-26-2005, 02:42 PM

If you're worried about it, create a shell function that calls ' find -name $1 \! -path "^/proc" '.

Actually, it would be useful to create one like ' find -name $1 \! -path "^/(proc|dev|lost+found|sys)" ' and call it findfile or something. Then you won't get useless results from system directories when you're looking for a file.

jbuckley2004 · 08-26-2005, 05:51 PM

Player_2,
I think I understand this...
It's a script that has one passes parameter ($1, right?) that calls the find function, and searches through every directory except /proc ??? is that right?

Um... my knowledge of bash is awful. Doesn't the -name come *after* the starting point of the path?

Either way, thanks. This is a useful idea/workaround.
J