Paul Collins <[EMAIL PROTECTED]> writes: > "J. Bruce Fields" <[EMAIL PROTECTED]> writes: > >> On Fri, Aug 01, 2008 at 11:15:33PM +1000, Aníbal Monsalve Salazar wrote: >>> On Mon, Jul 28, 2008 at 03:13:19AM -0400, Steve Dickson wrote: >>> >I just cut the 1.1.3 nfs-utils release. Unfortunately I'm having >>> >issues accessing my kernel.org account so for the moment the >>> >tar ball is only available on SourceForge: >>> > >>> > http://sourceforge.net/projects/nfs >>> >[...] >>> >>> 1.1.3 clients don't work with a 1.0.10 server anymore. >> >> Very weird--it might make sense if upgrading nfs-utils broke the mount >> itself, but here it seems the mount is succeeding and subsequent file >> access (which I'd expect to only involve the in-kernel client code) is >> failing. Maybe there's some difference in the mount options? What does >> /proc/self/mounts say? I assume these are all v2 or v3 mounts? > > I discovered today that I was no longer able to write to the v3 mount on > my 1.1.2 server. I checked /proc/mounts and noticed sec=null on the > mount. Either adding sec=sys to the client's mount options or > downgrading to nfs-common 1.1.2 on the client fixes the problem.
Adding sec=sys fixes my computer too. Perhaps it should be documented somewhere in /usr/share/doc/nfs-common/? Regards /Rasmus -- Rasmus Bøg Hansen MSC Aps Bøgesvinget 8 2740 Skovlunde 44 53 93 66 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
