LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Reply
 
Search this Thread
Old 08-23-2005, 04:24 PM   #1
jbuckley2004
Member
 
Registered: Aug 2004
Distribution: Mandriva 2008 One
Posts: 124

Rep: Reputation: 17
Problem with the #find command


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
 
Old 08-23-2005, 05:51 PM   #2
flower.Hercules
Member
 
Registered: Aug 2005
Distribution: Gentoo
Posts: 228

Rep: Reputation: 31
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
 
Old 08-24-2005, 08:04 AM   #3
jbuckley2004
Member
 
Registered: Aug 2004
Distribution: Mandriva 2008 One
Posts: 124

Original Poster
Rep: Reputation: 17
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.
 
Old 08-24-2005, 09:30 AM   #4
addy86
Member
 
Registered: Nov 2004
Location: Germany
Distribution: Debian Testing
Posts: 332

Rep: Reputation: 31
Have a look at:
http://lists.debian.org/debian-user/.../msg04340.html
 
Old 08-24-2005, 07:50 PM   #5
jbuckley2004
Member
 
Registered: Aug 2004
Distribution: Mandriva 2008 One
Posts: 124

Original Poster
Rep: Reputation: 17
Addy86 -
Thanks. You hit on it exactly (and cliearly, I"m not alone with this little bug). It's time to report it.
J
 
Old 08-26-2005, 02:16 PM   #6
txtedmacs
LQ Newbie
 
Registered: Aug 2005
Location: N.E. U.S.A.
Distribution: Ubuntu 05.10, 6.06 also have used: FC 3, 4 & 5
Posts: 15

Rep: Reputation: 0
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!
 
Old 08-26-2005, 02:42 PM   #7
player_2
Member
 
Registered: Aug 2003
Posts: 57

Rep: Reputation: 15
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.
 
Old 08-26-2005, 05:51 PM   #8
jbuckley2004
Member
 
Registered: Aug 2004
Distribution: Mandriva 2008 One
Posts: 124

Original Poster
Rep: Reputation: 17
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
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Find/grep command to find matching files, print filename, then print matching content stefanlasiewski Programming 8 12-18-2013 05:36 PM
who to use find command NalinA Linux - Newbie 2 10-25-2005 08:08 AM
find command jch02140 Linux - Newbie 2 07-19-2005 12:21 AM
problem with the shell command "find zosimus Linux - Software 7 06-14-2005 04:28 PM
problem with find command in script cojo Linux - Software 3 05-26-2004 10:28 AM


All times are GMT -5. The time now is 03:16 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration