find: /proc/xxxx/task: No such file or directory
Hi,
Whenever I use find, the following error is always outputted: Code:
find: /proc/xxxx/task: No such file or directory Code:
find: /proc/xxxx/task: No such file or directory Code:
cd /proc/xxxx/task |
Does /proc/xxxx itself exist? It may be this is the process for the find itself so of course when you go to ls after the fact it is no longer there.
I don't see this problem when I do "find /proc". Exactly what are flags/arguments are you giving to find? |
Quote:
Quote:
Code:
[root@dedicated ~]# find / -name "account_info" Code:
[root@dedicated ~]# ls /proc/16374/ Code:
[root@dedicated ~]# find / -name "tsm_conf" |
I was able to get something similar:
find / -fstype ext3 >/dev/null find: /proc/2307/task/2307/fd/4: No such file or directory find: /proc/2307/fd/4: No such file or directory However I opened a second window when I started the find and did "ps -ef |grep find" which returned: root 2307 2101 10 14:20 pts/4 00:00:02 find / -fstype ext3 root 2313 2278 0 14:20 pts/5 00:00:00 grep find Meaning find was complaining about its own PID (2307). This makes some sense as its state would be changing at the moment it tried to read it. It is for such system specialized filesystems (/proc, /sys) that I exclude them from things like backups because this kind of error is quite common since they really aren't disk partition filesystems but rather memory structures Linux is showing as if they were filesystems. |
Good idea, jlightner. The process id find is giving me is 16374, so I did
Code:
[admin1@dedicated ~]$ ps -ef |grep 16374 |
defunct is the same as a zombie process. Defunct/zombie processes are essentially "dead" so can't be killed. They are usually waiting for a signal from their parent process ID. On SOME occasions you can get rid of them by getting rid of the parent. The PPID is 2075 so you can check to see what has PID 2075 for a clue as to what this a child of. You may be able kill 2075 and see the child go away.
(Killing the parent will either make it go away or change its PPID to 1 which is init. If it goes to 1 the only way it would go away is at your next reboot.) It isn't unusual to see a few defunct processes and they aren't really a problem in and of themselves. If however you saw dozens of such processes (especially if they all had the same PPID other than 1) it might indicate you have something attempting to spawn children that can't run properly. The fact that you see "perl" in the process suggests some Perl script is the parent. ps -ef |grep 2075 |
All times are GMT -5. The time now is 02:01 AM. |