Greetings, I'm running the following configuration: SUSE 10 (i586) Kernel: 2.6.13-15-default Hardware: Dell Precision Laptop As root, if I run "find" (searching any path and/or name), I get the following error: find: WARNING: Hard link count is wrong for /proc: this may be a bug in your filesystem driver. I checked the knowledge base and found this entry: ############## UnitedLinux 1.0 iA64 Service Pack 2 SuSE Linux Maintenance Web (2c8caf05239362c3cab351f3f40b9d5d) applies to SuSE Linux Enterprise Server 8 for IPF fix root access to /proc/<pid>/environ ############### Does the above service pack apply to my configuration and the "Hard link count error"? Does anyone have any additional information related to the error I'm seeing? Any help would be greatly appreciated. Mike Badar ESRI-Denver 1 International Court Broomfield, CO 80021-3200 303-449-7779 mbadar@esri.com www.esri.com
On Tuesday 02 May 2006 18:16, Mike Badar wrote:
Greetings,
I'm running the following configuration:
SUSE 10 (i586) Kernel: 2.6.13-15-default Hardware: Dell Precision Laptop
As root, if I run "find" (searching any path and/or name), I get the following error:
find: WARNING: Hard link count is wrong for /proc: this may be a bug in your filesystem driver.
I checked the knowledge base and found this entry:
It could simply be that the link count is read, then when the directory is read the number of files that would link has changed. Remember that entries in /proc come and go as processes come and go. I suspect that there is no problem. Just curious: why run find on /proc? -- Roger Oberholtzer OPQ Systems AB
On Wed, 2006-05-03 at 08:21 +0200, Roger Oberholtzer wrote:
On Tuesday 02 May 2006 18:16, Mike Badar wrote:
Greetings,
I'm running the following configuration:
SUSE 10 (i586) Kernel: 2.6.13-15-default Hardware: Dell Precision Laptop
As root, if I run "find" (searching any path and/or name), I get the following error:
find: WARNING: Hard link count is wrong for /proc: this may be a bug in your filesystem driver.
I checked the knowledge base and found this entry:
It could simply be that the link count is read, then when the directory is read the number of files that would link has changed. Remember that entries in /proc come and go as processes come and go. I suspect that there is no problem. Just curious: why run find on /proc?
A good question because it never used to happen, so how has the file system
or find changed?
If you don't know approximately where a file is the most obvious way to
look for it would be "find / -name whatever". So why does find
search /proc ?
--
Dave Cotton
participants (3)
-
Dave Cotton -
Mike Badar -
Roger Oberholtzer