[lkml]   [2001]   [Dec]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: NFS woes in 2.5.1-pre8
On Wed, Dec 12, 2001 at 10:02:01PM +0100, Trond Myklebust wrote:
> There are (as of yet) no changes to the NFS client in 2.5.x.
> Do you have any idea which syscall the above EIO is coming from? From
> your tcpdump, it didn't appear to be coming from the server, and the
> file attributes are getting displayed...

Ok, I've just seen it again. Here's the call that's failing:

lstat("../lib/", 0xbffffb98) = -1 EIO (Input/output error)

It seems that sometimes I can provoke it 4 or more times in a row, other
times no matter how hard I try, I can't. "4 times in a row" here means
umounting and then remounting the export on the assabet.

As I mentioned in my last (private) mail, the setup was slightly different
from my first description.

flint (nfs client) is responsible for writing these files onto the NFS server
(raistlin), and the programs are run on assabet (nfs client).

kernel 2.2.18-cdhs (raid)

mount indicates:
raistlin:/usr/src on /net/raistlin/src type nfs (rw,rsize=4096,wsize=4096,addr=

kernel 2.4.16
universal NFS server 2.2beta48

raistlin's exports file looks similar to the following:

/usr/src flint(rw,no_root_squash)
/usr/src/v2.5 assabet(ro)

kernel 2.5.1-pre10

mount indicates:
raistlin:/usr/src/v2.5 on /usr/src/v2.5 type nfs (ro,nolock,addr=

Russell King ( The developer of ARM Linux

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:14    [W:0.069 / U:0.436 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site