sfs unmount causes NFS wierdness

Bernhard Mogens Ege <[email protected]> Fri, 22 Oct 2004 13:00:43 +0200
Newsgroups gmane.comp.file-systems.sfs.general
Message-ID <[email protected]>
Short version: When sfscd is running (/etc/rc.d/init.d/sfscd start) on
a client that has a non-related nfs mount established (automount or
pure nfs doesn't matter) and a bash with cwd on the nfs mount, it (the
nfs mount) will give a stale nfs handle when left unused for about
17-19 minutes.

The setup is Redhat Fedora Core 2 running sfs-0.7.2 (and now 0.8pre
but that gives the same problem). The nfs mount on the client is setup
in /etc/fstab and is mounted from another FC2 pc. No sfs login is
created, the sfs client was just started and nothing more. When the
nfs mount is left alone for about 17-19 minutes, it will result in a
stale nfs handle. If actively used constantly, no stale nfs handle is
received.

Stopping the sfs client mounter (/etc/rc.d/init.d/sfscd stop) also
prevents the stale nfs handle from occuring even if the nfs mount is
never accessed.

Somehow sfsrwcd or nfsmounter are affecting normal nfs mounts on
fedora core 2 (kernel 2.6.8-1.521).

In var log messages these messages originating from the sfs client
startup are seen:

Oct 21 17:20:49 overmind sfscd: sfscd startup succeeded
Oct 21 17:20:49 overmind : sfscd: version 0.8pre, pid 3352
Oct 21 17:20:50 overmind : sfscd: not dropping privileges for debugging
Oct 21 17:20:51 overmind : sfsrocd: version 0.8pre, pid 3357
Oct 21 17:20:52 overmind : nfsmounter: version 0.8pre, pid 3358
Oct 21 17:20:52 overmind : nfsmounter: mounted /sfs
Oct 21 17:20:52 overmind : nfsmounter: mounted /sfs/.mnt/wait
Oct 21 17:20:52 overmind kernel: nfs warning: mount version older than kernel
Oct 21 17:20:52 overmind kernel: nfs warning: mount version older than kernel
Oct 21 17:20:52 overmind : sfsrwcd: version 0.8pre, pid 3356
Oct 21 17:21:03 overmind kernel: nfs warning: mount version older than kernel
Oct 21 17:21:03 overmind : nfsmounter: mounted /sfs/.mnt/0

Obviously the kernel sees a problem about the way sfs is trying to
mount /sfs. Could this be the reason? I really don't know why this
problem occurs but it is preventing us to use sfs properly.

Bernhard