Re: Help in setting up sfs server

> Date: Thu, 6 Mar 2003 09:21:00 -0600 (CST)
> From: Jeson Martajaya <jeson@xxxxxxxxxxxxx>
> 
> Thank you for your reply. I seem to fix the problem by NFS mount only
> the root (and not the subdir). My showmount shows this:
> [root@frontend-0 sbin]# showmount -e
> Export list for frontend-0:
> /export         129.116.206.112/255.255.255.248
> /usr/local/lsf  129.116.206.112/255.255.255.248
> /export/home    129.116.206.112/255.255.255.248,129.116.206.92
> /tmp/CHORD/root frontend-0  <---CHORD/root IS MOUNTED
> 
> After I set this up, One BIG question arise. is sfs-0.7.2 compatible with
> nfs3 ? It is because I have this error:

SFS indeed requires NFS3.

> rexd: spawning /tmp/CHORD/sfs-build/lib/sfs-0.7.2/ptyd
> sfsauthd: serving
> @frontend-0.tacc.utexas.edu,tx7ax73sy82ndq26zkytpjyuktsrf86p
> sfsrwsd: fatal: filesrv::finish: nfs3_transres encode failed (err 10001)
> sfssd: EOF from server

Not sure what is causing this.  One possibility is that your NFS3 file
handles are 64 bytes.  SFS doesn't really work with file handles
longer than 48 bytes.  At one point I think there was a bug in
ReiserFS that caused it to generate 64-byte file handles even though
they didn't really require that.

The way to check this is to run:

  env ACLNT_TRACE=10 sfssd -d >& /tmp/logfile

and then check the contents of /tmp/logfile.  Look for data structures
of type nfs_fh3 and see what the length is.

David