On Thu, Feb 24, 2011 at 06:06:00PM +0100, Ferenc Wagner wrote: > "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? -ominorversion=1 > > (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: There's no separate config option, but the kernel keeps it off by default. I think nfs-utils is overriding the kernel's default. We should fix that. --b. -- 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
