Bug 160253 - Hard link count is wrong for /proc: this may be a bug in your filesystem driver.
Hard link count is wrong for /proc: this may be a bug in your filesystem driver.
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
4
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Alexander Viro
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-13 16:48 EDT by Fabrizio Bersani
Modified: 2007-11-30 17:11 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-11-12 01:38:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Fabrizio Bersani 2005-06-13 16:48:40 EDT
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
Password:
[root@localhost fabrizio]# find / -name amarok-1.3-beta1.tar.bz2
/tmp/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.
/home/fabrizio/Desktop/amarok-1.3-beta1.tar.bz2


Version-Release number of selected component (if applicable):
findutils-4.2.20-1

How reproducible:
Always

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. ..."
  

Additional info:
Comment 1 Tim Waugh 2005-06-15 06:16:19 EDT
                  /* 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.
                   */
Comment 2 Alan Lehman 2005-06-20 00:32:52 EDT
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.
Comment 3 Dave Jones 2005-06-27 19:23:45 EDT
Mass update of -test bugs to update version to fc4.
(Please retest on final release, and report results if you have not already done
so).

Thanks.
Comment 4 Dave Jones 2005-07-15 17:16:25 EDT
[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
kudzu


Thank you.
Comment 5 Erik P. Olsen 2005-08-15 09:08:55 EDT
I have got the same problem with kernel 2.6.12-1.1398_FC4 after:
find / *plug* | grep jre

I run x86_64.
Comment 6 Dave Jones 2005-08-15 14:47:50 EDT
Should be fixed in the current kernel in updates-testing. (2.6.12-1.1420_FC4)
Comment 7 Dave Jones 2005-11-10 14:26:25 EST
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.

Thank you.
Comment 8 Andrew Zitnay 2005-11-11 08:14:42 EST
Fixed for me on 2.6.14-1.1637_FC4smp.

Drew

Note You need to log in before you can comment on or make changes to this bug.