From: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: statd for NFSv4 does not create file
Date: Thu, 14 Jul 2005 09:21:22 -0400
Message-ID: <1121347282.8202.49.camel@lade.trondhjem.org>
References: <20050714125536.788.qmail@web51609.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain
Cc: nfs@lists.sourceforge.net, steved@redhat.com
To: mehta kiran <kiranmehta1981@yahoo.com>
In-Reply-To: <20050714125536.788.qmail@web51609.mail.yahoo.com>
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

to den 14.07.2005 Klokka 05:55 (-0700) skreiv mehta kiran:
> Hi , 
>         I have observed the following.
>         RHEL4 GA and U1 
>         client accesses filesystem exported
>         by server using nfsv4 .
> 
>         It takes lock  on a file.
>         Other clients on "different" systems
>         get NFSERR_DENIED and they retry to acquire
>         lock.
> 
>         When first client release lock , other client
>         gets the lock.
>         But when i see in /var/lib/nfs/statd/sm 
>         directory , i cannot see any file with
>         name = server's name.

An NFSv4 client has no use for statd. The NFSv4 protocol has its own
methods for tracking client and server reboots.

Cheers,
  Trond


-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs