Hi All, Any idea why SuSE 9.3 would give me this warning every time I run find? I am using ext3 for filesystems instead of the default reiserfs. Never seen this before in other distros such as Fedora Core, Mandriva, CentOS. 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. Thanks, Phil
Phil, On Tuesday 23 August 2005 03:26, Phil Savoie wrote:
Hi All,
Any idea why SuSE 9.3 would give me this warning every time I run find? I am using ext3 for filesystems instead of the default reiserfs. Never seen this before in other distros such as Fedora Core, Mandriva, CentOS.
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.
It's not a bug in the file system code. It certainly has nothing to do with Reiser or XFS or ext3 or whatever file systems you're using, since the /proc file system is synthesized by the kernel and does not exist as a regular on-disk file system. If there's a bug, it's that "find" is not smart enough to know that /proc doesn't obey the usual rules and suppress that diagnostic or deal with it in some more intelligent way. At least we got them to fix find's bad behavior for file systems auto-mounted in /media.
Thanks,
Phil
Randall Schulz
As I remember there is a variable that you can set so SuSEconfig will
not set find and locate not to look at. However, I have the same
issue because my SuSE9.3 keeps finding no floppy and I have limited it
in /etc/sysconfig.
It seems that find is looking at /etc/fstab.
On Tue, 23 Aug 2005 07:06:23 -0700
Randall R Schulz
Phil,
On Tuesday 23 August 2005 03:26, Phil Savoie wrote:
Hi All,
Any idea why SuSE 9.3 would give me this warning every time I run find? I am using ext3 for filesystems instead of the default reiserfs. Never seen this before in other distros such as Fedora Core, Mandriva, CentOS.
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.
It's not a bug in the file system code. It certainly has nothing to do with Reiser or XFS or ext3 or whatever file systems you're using, since the /proc file system is synthesized by the kernel and does not exist as a regular on-disk file system.
If there's a bug, it's that "find" is not smart enough to know that /proc doesn't obey the usual rules and suppress that diagnostic or deal with it in some more intelligent way.
At least we got them to fix find's bad behavior for file systems auto-mounted in /media.
Thanks,
Phil
Randall Schulz
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
73 de Donn Washburn Hpage: " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB Email: " n5xwb@hal-pc.org " 307 Savoy St. HAMs: " n5xwb@arrl.net " Sugar Land, TX 77478 BMWMOA #: 4146 LL# 1.281.242.3256 " http://counter.li.org " #279316
On Tuesday 23 August 2005 10:06, Randall R Schulz wrote:
Phil,
On Tuesday 23 August 2005 03:26, Phil Savoie wrote:
Hi All,
Any idea why SuSE 9.3 would give me this warning every time I run find? I am using ext3 for filesystems instead of the default reiserfs. Never seen this before in other distros such as Fedora Core, Mandriva, CentOS.
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.
It's not a bug in the file system code. It certainly has nothing to do with Reiser or XFS or ext3 or whatever file systems you're using, since the /proc file system is synthesized by the kernel and does not exist as a regular on-disk file system.
If there's a bug, it's that "find" is not smart enough to know that /proc doesn't obey the usual rules and suppress that diagnostic or deal with it in some more intelligent way.
At least we got them to fix find's bad behavior for file systems auto-mounted in /media.
Thanks,
Phil
Randall Schulz
Hi Randall, Thanks for the reply. Just seems strange that I get this only on SuSE as opposed to the distros I had previously mentioned. Makes sense probably a different find utility SuSE uses? Phil
participants (3)
-
Donn L Washburn
-
Phil Savoie
-
Randall R Schulz