"J. Bruce Fields" <bfields@xxxxxxxxxxxx> writes: > On Tue, Feb 22, 2011 at 06:05:14PM +0100, Ferenc Wagner wrote: > >> "J. Bruce Fields" <bfields@xxxxxxxxxxxx> writes: >> >>> - In the NFSv4.1 case there is a "reclaim complete" rpc that >>> clients are required to send. Currently we don't take >>> advantage of that to end the grace period early, but we >>> should. That's no help for 4.0 clients. >> >> /proc/fs/nfsd/versions shows +4.1 on the server, does this mean that >> nfs4 type Linux client mounts should issue "reclaim complete"? > > It means that a 4.1 is supported, so a client *could* use 4.1 if it > asked to. And if it did use 4.1, yes, it would be required to issue > reclaim complete. Current linux clients do not use 4.1 unless you > explicitly ask for it on the mount commandline. I can't find any mention of 4.1 in man nfs (nfs-common version 1.2.2), is there an undocumented nfsvers=4.1 mount option or some other means? > (Aside: the server really shouldn't have +4.1 by default, as the 4.1 > server is not done. We should fix that; which distro are you using?) Debian squeeze. If it's switchable, then it's possible I switched it on, I can't remember. However, 4.1 client support is disabled in the stock kernel config, and 4.1 server support isn't even mentioned: $ fgrep NFS /boot/config-2.6.32-5-686 CONFIG_NFS_FS=m CONFIG_NFS_V3=y CONFIG_NFS_V3_ACL=y CONFIG_NFS_V4=y # CONFIG_NFS_V4_1 is not set CONFIG_NFS_FSCACHE=y CONFIG_NFSD=m CONFIG_NFSD_V2_ACL=y CONFIG_NFSD_V3=y CONFIG_NFSD_V3_ACL=y CONFIG_NFSD_V4=y CONFIG_NFS_ACL_SUPPORT=m CONFIG_NFS_COMMON=y CONFIG_NCPFS_NFS_NS=y >> Does the Linux nfs server implementation use the lease time of the >> previous server instance as grace period on startup, or does it >> simply take whatever it finds in /proc/fs/nfsd/nfsv4leasetime? > > The latest server has separately tunable "nfsv4gracetime" and > "nfsv4leasetime", and if you want to be careful, you should: > > - stop the server > - set nfsv4gracetime to the *previous* lease time > - set nfsv4leasetime to the *new* lease time > - start the server > > That gives you the new (lower) lease time while still giving a > sufficiently long grace period for clients who only knew about the old > time to recover. After doing that once, on future restarts you can use > the shorter time for both. Yes, this is exactly where I was going to (and what's recommended in the RFC). Good to hear it's already implemented! > Probably we should write utilites which do this right for you.... No worries, I won't be changing the lease time that frequently. :) -- Thanks a lot, Feri. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
