On Wed, Feb 13, 2013 at 10:05:09AM -0500, J. Bruce Fields wrote: > On Tue, Feb 12, 2013 at 07:28:49PM -0500, Steve Dickson wrote: > > > > > > On 12/02/13 19:21, J. Bruce Fields wrote: > > > On Tue, Feb 12, 2013 at 07:11:41PM -0500, J. Bruce Fields wrote: > > >> I get failures on NFSv4 mounts after applying these patches. > > >> > > >> # mount -tnfs4 pip1:/exports/ext4 /mnt/ > > >> mount.nfs4: mounting pip1:/exports/ext4 failed, reason given by server: No such file or directory > > >> > > >> In wireshark I don't see an error, but I do notice that the final > > >> rpc request and reply is a getattr with bitmap 0, which is odd. > > > > > > Oh, and that was a build with labeled nfs configured out. > > Drop the -tnfs4 option... > > Well, sure, then it'll negotiate down to v3 and the mount will succeed. > > But if you request v4 (either with -tnfs4 or -onfsvers=4), it fails. > > In other words, these patches break NFSv4 mounts in the default > (CONFIG_NFS_V4_SECURITY_LABEL=n) case. Also, the problem starts with "NFS: Client Implementation of Labeled-NFS". --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
