Red Hat Bugzilla – Bug 160253
Hard link count is wrong for /proc: this may be a bug in your filesystem driver.
Last modified: 2007-11-30 17:11:07 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050504 Fedora/1.0.3-4 Firefox/1.0.3
Description of problem:
[fabrizio@localhost ~]$ su
[root@localhost fabrizio]# find / -name amarok-1.3-beta1.tar.bz2
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.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.download a file from example from http://prdownloads.sourceforge.net/amarok/amarok-1.3-beta1.tar.bz2?use_mirror=switch
2. try to locate the directory where it has been downloaded "find / -name amarok-1.3-beta1.tar.bz2"
3. you get the error message: "Hard link count is wrong for /proc: this may be a bug in your filesystem driver. ..."
/* This is a subdirectory, but the number of directories we
* have found now exceeds the number we would expect given
* the hard link count on the parent. This is likely to be
* a bug in the filesystem driver (e.g. Linux's
* /proc filesystem) or may just be a fact that the OS
* doesn't really handle hard links with Unix semantics.
* In the latter case, -noleaf should be used routinely.
Problem persists in FC4 and occurs with any 'find -name'. -noleaf prevents the
error. Exact message:
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.
Mass update of -test bugs to update version to fc4.
(Please retest on final release, and report results if you have not already done
[This comment has been added as a mass update for all FC4 kernel bugs.
If you have migrated this bug from an FC3 bug today, ignore this comment.]
Please retest your problem with todays 2.6.12-1.1398_FC4 update.
If your problem involved being unable to boot, or some hardware not being
detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE*
installing any kernel updates.
If in doubt, you can recreate this file using..
mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak
mv /etc/modprobe.conf /etc/modprobe.conf.bak
I have got the same problem with kernel 2.6.12-1.1398_FC4 after:
find / *plug* | grep jre
I run x86_64.
Should be fixed in the current kernel in updates-testing. (2.6.12-1.1420_FC4)
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.
Fixed for me on 2.6.14-1.1637_FC4smp.