From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: find: WARNING: Hard link count is wrong for /proc/1
Date: Mon, 2 Jun 2008 08:31:19 +0200 [thread overview]
Message-ID: <19f34abd0806012331m7c57468bu820e9b6b0184836d@mail.gmail.com> (raw)
Hi,
2.6.26-rc4 seems to exhibit the following (new since at least 2.6.24)
warning when running find /proc/1:
find: WARNING: Hard link count is wrong for /proc/1: 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.
# ls -l /proc/1
total 0
-r-------- 1 root root 0 Jun 2 02:20 auxv
--w------- 1 root root 0 Jun 2 02:20 clear_refs
-r--r--r-- 1 root root 0 Jun 2 02:20 cmdline
-rw-r--r-- 1 root root 0 Jun 2 02:20 coredump_filter
lrwxrwxrwx 1 root root 0 Jun 2 02:20 cwd -> /
-r-------- 1 root root 0 Jun 2 02:20 environ
lrwxrwxrwx 1 root root 0 Jun 2 02:20 exe -> /bin/bash
dr-x------ 2 root root 0 Jun 2 02:20 fd
dr-x------ 2 root root 0 Jun 2 02:20 fdinfo
-r-------- 1 root root 0 Jun 2 02:20 limits
-r--r--r-- 1 root root 0 Jun 2 02:20 maps
-rw------- 1 root root 0 Jun 2 02:20 mem
-r--r--r-- 1 root root 0 Jun 2 02:20 mountinfo
-r--r--r-- 1 root root 0 Jun 2 02:20 mounts
-r-------- 1 root root 0 Jun 2 02:20 mountstats
dr-xr-xr-x 5 root root 0 Jun 2 02:20 net
-rw-r--r-- 1 root root 0 Jun 2 02:20 oom_adj
-r--r--r-- 1 root root 0 Jun 2 02:20 oom_score
-r-------- 1 root root 0 Jun 2 02:20 pagemap
lrwxrwxrwx 1 root root 0 Jun 2 02:20 root -> /
-r--r--r-- 1 root root 0 Jun 2 02:20 smaps
-r--r--r-- 1 root root 0 Jun 2 02:20 stat
-r--r--r-- 1 root root 0 Jun 2 02:20 statm
-r--r--r-- 1 root root 0 Jun 2 02:20 status
dr-xr-xr-x 3 root root 0 Jun 2 02:20 task
-r--r--r-- 1 root root 0 Jun 2 02:20 wchan
# stat /proc/1
File: `/proc/1'
Size: 0 Blocks: 0 IO Block: 1024 directory
Device: 3h/3d Inode: 39 Links: 5
Access: (0555/dr-xr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2008-06-02 02:19:07.418398897 -0400
Modify: 2008-06-02 02:19:07.418398897 -0400
Change: 2008-06-02 02:19:07.418398897 -0400
The other /proc/pid entries seem to have the same problem.
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next reply other threads:[~2008-06-02 6:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 6:31 Vegard Nossum [this message]
2008-06-02 7:00 ` Vegard Nossum
2008-06-02 7:03 ` Vegard Nossum
2008-06-02 15:53 ` Jan Kara
2008-06-02 16:11 ` Pekka Enberg
2008-06-02 16:14 ` Pekka Enberg
2008-06-03 1:59 ` Eric W. Biederman
2008-06-03 2:10 ` Andrew Morton
[not found] ` <m1fxrv18q2.fsf@x61.ebiederm.org>
2008-06-03 4:06 ` Vegard Nossum
2008-06-02 22:29 ` Rafael C. de Almeida
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19f34abd0806012331m7c57468bu820e9b6b0184836d@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®