Re: /var/lib/nfs/v4recovery

["J. Bruce Fields" <bfields@fieldses.org>]

On Thu, Mar 09, 2006 at 11:18:03PM -0800, mehta kiran wrote:
>    I could see that it is mentioned that
>    /var/lib/nfs/v4recovery needs to be created
>    for NFSv4 at 
>  
> http://www.citi.umich.edu/projects/nfsv4/linux/using-nfsv4.html.

We've had some negative feedback on the way we're storing persistant
state for reboot recovery.  Among other problems:
	- There's an objection (which I don't entirely claim to
	  understand) against nfsd doing directory operations in the
	  kernel
	- It doesn't give any chance for synchronous callouts for, e.g.,
	  mirroring the data to a backup server for failover, whereas
	  the standard statd stuff does.

Hopefully this will fixed by 2.6.17 or 2.6.18.

>    1. What is this file for ?
>       As NFSv4 uses lease based locking , it does
>       create files on persistent storage.
>       And its state could be stored   
>       in /var/lib/nfs/statd/state , right ?

I don't think we can store the state in exactly the same place, but we
probably will move to something more similar to statd.

>    2. I have read that lease time for NFSV4 can be 
>       chnaged by setting value in
>       /proc/fs/nfsd/nfsv4leasetime. In case i dont
>       set lease period  , is grace period set by user
>       considered as the lease time ?

Since we use leases to implement delegations, there's an ugly conflict
between /proc/sys/fs/lease-break-time and /proc/fs/nfsd/nfsv4leasetime,
which we're currently working on fixing.

--b.


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs