Re: Write to nfs fs gives I/O Error

Tony Lill (ajlill@ajlc.waterloo.on.ca)
Fri, 28 Nov 1997 17:34:30 EST

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Daniel Ryde: "Re: Let's test: [Re: Memory leak in kernel 2.0.32pre1.]"
Previous message: Dean Gaudet: "Re: broken pipes in tar on large files"
Maybe in reply to: Tony Lill: "Write to nfs fs gives I/O Error"
Next in thread: Bill Hawes: "Re: Write to nfs fs gives I/O Error"

>>>>> "Bill" == Bill Hawes <whawes@star.net> writes:
Bill> In 2.1.66 I've added some diagnostics to start tracking down
Bill> the unspecified EIO errors, so that may help show what's
Bill> wrong. What I need is for you to run tests and see if any of
Bill> the printks are triggered, and then I can analyze it
Bill> further.

Here you go. matrix is the Unixware server, slug is the client.

Nov 28 17:27:48 matrix unix: nfs_server: bad getargs
Nov 28 17:27:48 slug.ajlc.waterloo.on.ca slug kernel: RPC: garbage, exit EIO
Nov 28 17:27:49 matrix unix: nfs_server: bad getargs
Nov 28 17:27:53 matrix last message repeated 2 times
Nov 28 17:27:53 slug.ajlc.waterloo.on.ca slug last message repeated 3 times
Nov 28 17:28:06 matrix unix: nfs_server: bad getargs
Nov 28 17:28:06 slug.ajlc.waterloo.on.ca slug kernel: RPC: garbage, exit EIO

Also, I've been getting these in .65 and .66, they don't appear to be
related to the EIO's, but what do I know.

Nov 28 17:28:15 slug.ajlc.waterloo.on.ca slug kernel: nfsd_d_validate: invalid length -252605915

Bill> Regards, Bill

Next message: Daniel Ryde: "Re: Let's test: [Re: Memory leak in kernel 2.0.32pre1.]"
Previous message: Dean Gaudet: "Re: broken pipes in tar on large files"
Maybe in reply to: Tony Lill: "Write to nfs fs gives I/O Error"
Next in thread: Bill Hawes: "Re: Write to nfs fs gives I/O Error"