Re: Help in setting up sfs server

> Date: Thu, 6 Mar 2003 09:46:21 -0600 (CST)
> From: Jeson Martajaya <jeson@xxxxxxxxxxxxx>
> 
> 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] {
> 
> 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?)

It's not a serious bug, but it will prevent SFS from working.

> SFS 0.7.2 works with nfs2 right?

No, but since reiserFS supports NFS2, and NFS2 has 32-byte file
handles, there is really no reason the NFS3 implementation should
require 64-byte file handles--32-byte NFS2 file handles are already
sufficient to identify files uniquely.

Looking back over old email, this may not be a reiserfs bug, but
rather a generic linux problem.  For the 2.4.10 kernel, at least, Chip
Salzenberg suggested this patch:

--- linux_o/fs/nfsd/nfsfh.c.old Thu Sep 20 21:02:01 2001
+++ linux/fs/nfsd/nfsfh.c       Tue Oct  2 15:46:47 2001
@@ -732,6 +732,8 @@
        struct super_block *sb = dentry->d_inode->i_sb;
        
-       if (dentry == exp->ex_dentry)
+       if (dentry == exp->ex_dentry) {
+               *maxsize = 0;
                return 0;
+       }
 
        if (sb->s_op->dentry_to_fh) {