Re: Help in setting up sfs server

I have run this:
env ACLNT_TRACE=10 /tmp/CHORD/sfs-build/sbin/sfssd -d >& /tmp/CHORD/sfsnfs3.log

nfs_fh3 ARGS = {
  opaque data<64> = [64] {
    01, 00, 00, 00, 00, 08, 00, 02,
    09, cc, 03, 00, 00, 00, 00, 00,
    00, 00, 00, 00, 00, 00, 00, 00,
    00, 00, 00, 00, 00, 00, 00, 00,
    00, 00, 00, 00, 00, 00, 00, 00,
    00, 00, 00, 00, 00, 00, 00, 00,
    ...
  };
};
sfsrwsd: ACLNT_TRACE: call nfs_program_3:NFSPROC3_GETATTR x=a
nfs_fh3 ARGS = {
  opaque data<64> = [64] {
    01, 00, 00, 00, 00, 08, 00, 02,
    09, cc, 03, 00, 00, 00, 00, 00,
    00, 00, 00, 00, 00, 00, 00, 00,
    00, 00, 00, 00, 00, 00, 00, 00,
    00, 00, 00, 00, 00, 00, 00, 00,
    00, 00, 00, 00, 00, 00, 00, 00,
    ...
  };
};

Does this really mean the NFS3/ReiserFS I have in my RH7.2 system has a
bug in it? (by having it running under 64 bits?)

SFS 0.7.2 works with nfs2 right?

-Jeson-


On Thu, 6 Mar 2003, David Mazieres wrote:

> > 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