Re: http://www.citi.umich.edu/projects/nfsv4/linux
I believe the proper directory to use for rpc_pipefs should be
/var/lib/nfs/rpc_pipefs (as in the sample idmapd.conf file), not
/var/lib/rpc_pipes as documented. This should be corrected where it
describes the entry in /etc/fstab as well as the mkdir command. Or, is the
documented directory fine to use as long as the sample idmapd.conf file is
updated to match? Either way, one of these needs to change, or at the very
least make a note on the website stating these need to match.
Also, the instructions for starting the daemons on both the server and
client are not quite correct- mountd, idmapd and nfsd should each be
prepended by "rpc.", for example, rpc.idmapd.
btw, I also discovered that on 2.6.1 with the latest patches from the
website (i.e. CITI_NFS4_ALL-3) with every kernel parameter mentioned on the
website compiled directly into the kernel my machine won't boot (last
message displayed is "NET: Registered protocol family 17"), but with
CONFIG_RPCSEC_GSS_KRB5=m the machine boots fine.
Still having a problem getting rpc.gssd started on the client ("GSSD:
Decrypt integrity check failed while getting initial ticket" followed by
"couldn't get krb5 machine ticket"), but that's probably a krb5
configuration problem on my part.
Regards,
---
Bruce Allan <[email protected]>
Software Engineer, Linux Technology Center
IBM Corporation, Beaverton OR
503-578-4187 IBM Tie-line 775-4187
On Thu, Feb 12, 2004 at 04:34:52PM -0800, Bruce Allan wrote:
> Re: http://www.citi.umich.edu/projects/nfsv4/linux
>
> I believe the proper directory to use for rpc_pipefs should be
> /var/lib/nfs/rpc_pipefs (as in the sample idmapd.conf file), not
> /var/lib/rpc_pipes as documented. This should be corrected where it
> describes the entry in /etc/fstab as well as the mkdir command.
Yep, fixed, thanks.
> Or, is the documented directory fine to use as long as the sample
> idmapd.conf file is updated to match?
That should be fine too.
> Also, the instructions for starting the daemons on both the server and
> client are not quite correct- mountd, idmapd and nfsd should each be
> prepended by "rpc.", for example, rpc.idmapd.
Yep, thanks for the correction.
> btw, I also discovered that on 2.6.1 with the latest patches from the
> website (i.e. CITI_NFS4_ALL-3) with every kernel parameter mentioned on the
> website compiled directly into the kernel my machine won't boot (last
> message displayed is "NET: Registered protocol family 17"), but with
> CONFIG_RPCSEC_GSS_KRB5=m the machine boots fine.
Yes, it's a known problem. Either turn off SMP support in your kernel,
or apply the appended patch, or just upgrade to the latest 2.6.2 CITI
patches, which were released today.
> Still having a problem getting rpc.gssd started on the client ("GSSD:
> Decrypt integrity check failed while getting initial ticket" followed by
> "couldn't get krb5 machine ticket"), but that's probably a krb5
> configuration problem on my part.
Hm, could be. If you'd like to give us more details on your setup
(krb5.conf, output from klist -k, ps output to make sure gssd is running
with the right options, etc), we could try to figure out what's going
on. [email protected] would probably be the best place to follow
up on that.--b.
diff -puN net/sunrpc/svcauth.c~neil_NfsdCacheImprove net/sunrpc/svcauth.c
--- linux-2.6.1/net/sunrpc/svcauth.c~neil_NfsdCacheImprove 2004-02-08 13:54:41.000000000 -0500
+++ linux-2.6.1-bfields/net/sunrpc/svcauth.c 2004-02-08 14:09:08.000000000 -0500
@@ -150,7 +150,11 @@ DefineCacheLookup(struct auth_domain,
&auth_domain_cache,
auth_domain_hash(item),
auth_domain_match(tmp, item),
- kfree(new); if(!set) return NULL;
+ kfree(new); if(!set) {
+ if (new) write_unlock(&auth_domain_cache.hash_lock);
+ else read_unlock(&auth_domain_cache.hash_lock);
+ return NULL;
+ }
new=item; atomic_inc(&new->h.refcnt),
/* no update */,
0 /* no inplace updates */
_
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs