On Fri, Feb 12, 2010 at 02:58:23PM -0500, Steve Dickson wrote: > > > On 02/05/2010 03:05 PM, J. Bruce Fields wrote: > > From: J. Bruce Fields <bfields@xxxxxxxxxxxxxx> > > > > The current kernel code should not be enabled by default, because it > > does not yet attempt to be a conform completely to the rfc; for example, > > some required pieces of protocol are missing. > > > > Therefore the kernel defaults to leaving minorversion1 off. When the > > code matures sufficiently, that default will change. > > > > That kernel default becomes meaningless if nfs-utils always explicitly > > turns 4.1 on or off. So, nfs-utils should by default do nothing. > > > > Early adopters that want to turn on NFSv4.1 explicitly can still do so > > using > > > > echo "+4.1" >/proc/fs/nfsd/versions > > > When I write to /proc/fs/nfsd/versions I'm getting > write error: Device or resource busy > > What did you do to make the file writeable? You just need to do it before starting nfsd. So if it's just a one-off experiment you could /etc/init.d/nfs-server stop echo "+4.1" >/proc/fs/nsfd/versions /etc/init.d/nfs-server start On machines where I was using 4.1 regularly I'd probably at a line to the init script, or to a local init script that ran before it. --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
