Re: BUG REPORT: kernel nfs between 2.4.19-pre2 (server) and 2.2.21-pre3 (client)

[Trond Myklebust <trond.myklebust@fys.uio.no>]

>>>>> " " == Stephan von Krawczynski <skraw@ithnet.com> writes:

     > Hello all, I just upgraded a host from 2.2.19 to 2.2.21-pre3
     > and discovered a problem with kernel nfs. Setup is this:

     > knfs-server is 2.4.19-pre2 knfs-client is 2.2.21-pre3

     > First mount some fs (mountpoint /backup). Then go and mount
     > some other fs from the same server (mountpoint /mnt), do some
     > i/o on the latter and umount it again. Now try to access
     > /backup. You see:
     > 1) /backup (as a fs) vanished, you get a stale nfs handle.
     > 2) umount /backup; mount /backup does not work. client tells
     >    "permission denied". server tells "rpc.mountd: getfh failed:
     >    Operation not permitted"

By 'some fs' do you mean ext2?

Not all filesystems work well with knfsd when things start to drop out
of the (d|i)caches. In particular things like /backup == VFAT might
give the above behaviour, since VFAT does not know how to map the NFS
file handles into on-disk inodes.

Cheers,
  Trond