> On Tue, 9 Nov 1999, Trond Myklebust wrote:
>> >>>>> " " == Olaf Flebbe <o.flebbe@science-computing.de>
>> >>>>> writes:
>>
>>
>> > But, the client (both plptools and amd) get an error message!
>> > This shouldn't be. What can a client to against it?
>>
>> Which error message do they get, and what are the mount options
>> being used?
> from an strace of an cp to the mounted dir
> write(5,
> "\310\223\372|7s\356!\215\245e\301o$\rG\356\36\270\230b"...,
> 4096) = -1 ENOSPC (No space left on device)
> (The diagnostic is incorrect)
Hmm. Strange...
1) Does the ordinary NFS client (no amd or plptools) give the same
error?
2) What about 'traceroute -s 256'? (Most versions of traceroute
should be able to interpret the NFS protocol, and tell you what is
being sent down the wire.) I'd like to know whether the server
really is replying ENOSPC, or whether there's a 'translation
error' somewhere...
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/