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? --b. > > Please read the Debian bug report at http://bugs.debian.org/492970 > > On Fri, Aug 01, 2008 at 02:54:02PM +0200, Christian Surchi wrote: > >On Wed, Jul 30, 2008 at 12:56:12PM +0200, Rasmus Bøg Hansen wrote: > >>Package: nfs-common > >>Version: 1:1.1.3-1 > >>Severity: important > >> > >> > >>Upgrading nfs-common 1:1.1.3-1 broke my NFS client. > >> > >>The NFS server is running etch and nothing was changed. After upgrading > >>the client to 1:1.1.3-1 access to my files (/home is NFS-mounted) is > >>disallowed where it should be allowed (and certainly was in 1:1.1.2-6). > > > >I confirm this one on my sid client too. No changes in nfs server > >(etch). Downgrading nfs-common solved the problem for me too. > > > >Christian > _______________________________________________ > NFSv4 mailing list > NFSv4@xxxxxxxxxxxxx > http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4 -- 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
