[lkml]   [2001]   [Oct]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectnfs_lookup_validate and dud inodes
I have an nfs server and a diskless client, both running 2.2.19 under
Debian. If I update files on the server, sometimes the client gets
confused about some files, and stays confused. For instance:

[larsi@sparky ~]$ ls -l /lib/libe2*
ls: /lib/ Input/output error
-rw-r--r-- 1 root root 13400 Sep 22 17:15 /lib/

This is what it looks like on the server:

[larsi@quimbies ~]$ ls -l /tftpboot/sparky/lib/*
lrwxrwxrwx 1 root root 13 Oct 30 20:23 /tftpboot/sparky/lib/ ->
-rw-r--r-- 1 root root 13400 Sep 22 17:15 /tftpboot/sparky/lib/

So the error message is when trying to access the symlink.

If I tell the nfs client to output debug messages:

# echo 65535 > /proc/sys/sunrpc/nfs_debug

I then get the following output:

nfs_lookup_validate: lib/ has dud inode
NFS: put_inode(1/1912607313)
NFS: lookup(lib/
NFS call lookup
NFS reply lookup: 0
NFS: nfs_fhget(lib/ fileid=1912607313)
NFS: __nfs_fhget(1/1912607313 ct=0)
NFS call lookup n
NFS reply lookup: 0

(I think this is the relevant part; it spews out quite a lot of data.)

There are no error messages in any of the log files on the server.

Is this a known bug?

(domestic pets only, the antidote for overdose, milk.) * Lars Magne Ingebrigtsen
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:12    [W:0.079 / U:0.004 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site