Hi Joachim
please find the below details as you requested,
# ls -li
total 1456
32 -rwx------ 1 root root 0 Nov 1 11:11 .hpshm_keyfile
205 -rw-r--r-- 1 root root 524346 Jan 4 12:50 SAN
8552449 drwxr-xr-x 2 root root 4096 Jan 4 12:49 Source
31 -rw-r--r-- 1 root root 8395 Jul 6 2006 adlagent.conf.default
19 drwxr-xr-x 2 root root 4096 Jul 6 2006 bin
20 drwxr-xr-x 3 root root 4096 Jan 4 17:57 boot
33 -rw-r--r-- 1 root root 121 Jan 4 12:05 config.log
696 drwxr-xr-x 12 root root 6680 Jan 21 15:22 dev
12 drwxr-xr-x 72 root root 8192 Jan 22 14:06 etc
267 -r--r--r-- 1 root root 283110 Jan 21 15:37
findutils-4.2.27-14.2.x86_64.rpm
265 -r--r--r-- 1 root root 84608 Jan 21 15:37
findutils-locate-4.2.27-14.2.x86_64.rpm
21 drwxr-xr-x 3 root root 4096 Jan 9 11:42 home
22 drwxr-xr-x 8 root root 4096 Jul 6 2006 lib
23 drwxr-xr-x 5 root root 4096 Jul 6 2006 lib64
11 drwx------ 2 root root 16384 Jul 6 2006 lost+found
1856 dr-xr-xr-x 6 root root 4096 Jul 6 2006 media
25 drwxr-xr-x 2 root root 4096 Jun 16 2006 mnt
18 drwxr-xr-x 9 root root 4096 Jan 4 17:02 opt
1 dr-xr-xr-x 127 root root 0 Jan 10 09:20 proc
26 drwx------ 21 root root 4096 Jan 22 14:51 root
27 drwxr-xr-x 3 root root 8192 Nov 1 11:10 sbin
28 drwxr-xr-x 4 root root 4096 Jul 6 2006 srv
1 drwxr-xr-x 11 root root 0 Jan 10 09:20 sys
29 drwxrwxrwt 8 root root 4096 Jan 22 15:04 tmp
17 drwxr-xr-x 13 root root 4096 Jan 4 12:59 usr
16 drwxr-xr-x 15 root root 4096 Jan 4 12:59 var
On 1/22/07, Joachim Schrod <[EMAIL PROTECTED]> wrote:
>>>>> "AK" == Anil Kalasa <[EMAIL PROTECTED]> writes:
AK> No it just works fine, with ls -ld command, only problem is when I use
AK> the command find.
AK> regarding file system everything else is wokring fine, only locate and
AK> find is not working.
AK> error as ...
AK> # find
AK> .
AK> ./lost+found
AK> find: ./etc: No such file or directory
AK> find: ./proc: No such file or directory
You mentioned that already; that doesn't help to identify your
problem. It's quite clear WHAT happens, but not WHY it happens.
That message appears when there is an entry in the directory list and
the inode of that entry could not be opened. The directory list only
contains the name and the inode number, so find knows that there
should something be there. But when the respective directory (e.g.,
/etc) shall be opened, the Linux filesystem returns ENOENT (no such
file or directory) since it doesn't find that inode.
As I wrote, that happens normally only with dangling symlinks or when
a file system is damaged.
And it's very strange that the lost+found directory could be opened,
but etc couldn't. So it's not a general problem with all directory
entries.
That's the reason why I asked for the output of ls -l / (actually, ls
-li / would be even better) and of stat /etc. Maybe one can get a clue
from that output. With the currently available information, the
probability of help for you is low.
Joachim
PS: Please answer only to the list. I don't read opensuse by email and
I don't want that stuff in my inbox. I also won't react faster when
you stuff my inbox, that just makes me loose interest in your problem.
Thanks.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod Email: [EMAIL PROTECTED]
Roedermark, Germany
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
