> knfsd (or kmountd?) works in a weird way anyway... Sometimes it refuses
> to satisfy mount request without obvious reason. Locking seems to always
> fail...
I tried 0.4.22 and kstatd, thanks for the tips. Locking seems to work
with statd, and I can actually mount if the exact path is exported,
i.e. it would not export subdirectories. Is it intentional?
Other things are worse. First, every now and then, when the client
(Solaris 2.5.1) goes for some data on the exported directory, I get
Aug 12 17:11:49 ariel kernel: svc: sk_data negative!
Aug 12 17:11:49 ariel kernel: RPC: bad TCP reclen 6320696e<4>nfsd: terminating on error 5
and the client says: "NFS server on ariel not responding, still trying".
In five minutes, it revives and continue to work.
Also, often there are these messages:
Aug 12 19:32:53 ariel kernel: svc: unknown version (3)
What is even worse, while reading files from a directory exported from
a Linux box seems to work (aside from the above), writing results in
corrupt file: the last block seems to be filled with junk.
Just thought that I should share my observations...
-- Eugene Crosser; 2:5020/230@fidonet; http://www.average.org/~crosser/- 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.altern.org/andrebalsa/doc/lkml-faq.html