Date: Wed, 30 Mar 2005 10:59:11 +0100 From: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> To: Tomi.Vainio@Sun.COM Cc: freebsd-current@freebsd.org Subject: Re: NFSv4 failure Message-ID: <1112176751.37667.5.camel@buffy.york.ac.uk> In-Reply-To: <16969.55339.169670.941190@ultrahot.finland.sun.com> References: <16969.43954.994530.751030@ultrahot.finland.sun.com> <20050329210714.GF51674@dan.emsphone.com> <16969.50345.585074.976772@ultrahot.finland.sun.com> <20050329214647.GG51674@dan.emsphone.com> <16969.55339.169670.941190@ultrahot.finland.sun.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2005-03-30 at 01:35 +0300, Tomi Vainio - Sun Finland wrote: > Dan Nelson writes: > > > > Actually, it looks like the nfsclient module includes the nfs4 sources. > > I have "options NFSCLIENT" in my kernel config file, and I can mount a > > local Solaris 10 box using mount_nfs4. Ethereal confirms that I'm > > talking NFSV4 over the wire. > > > > I'm not sure what the nfs4client module is supposed to do. Maybe it > > was standalone at some point but they got merged? > > > You are right. NFSv4 is already integrated so it didn't need any > extra stuff anymore. Still I have problem with domain id mapping > because all file permissions are for -1 nobody. > > # ls -ld local > drwxr-sr-x 23 4294967294 4294967294 512 Mar 6 11:25 local Yes - I also see this with NFSv4 against a NetApp filestore. Gavin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1112176751.37667.5.camel>