View previous topic :: View next topic |
Author |
Message |
wmark n00b
Joined: 28 Sep 2005 Posts: 17
|
Posted: Wed Feb 22, 2012 4:29 pm Post subject: |
|
|
If you're using the following
Code: | zcat /proc/config.gz | grep -i CONFIG_NFS_USE_NEW_IDMAPPER
CONFIG_NFS_USE_NEW_IDMAPPER=y |
... then compile nfs-utils with NFSv41 support and add this line at the very top to /etc/request-key.conf:
Quote: | create id_resolver * * /usr/sbin/nfsidmap %k %d 600 |
... or else "upcalls" won't work. You will run into error messages (and all files will be owned by 'nobody') if you have not set a domain name, yet. Please see this follow-up post on how to do that. _________________ http://mark.ossdl.de/ |
|
Back to top |
|
|
depontius Advocate
Joined: 05 May 2004 Posts: 3509
|
Posted: Wed Feb 22, 2012 5:04 pm Post subject: |
|
|
I just ran "make xconfig" to take a look, and it doesn't appear that NFS_USE_NEW_IDMAPPER requires NFS_V4_1. When I look at /usr/src/linux/Documentation/filesystems/nfs/idmapper.txt I don't see anything about nfsv4.1 being required. (To be fair, I don't see anything about nfsv4 being required, either.) I though nfsv4.1 was primarily for larger-scale and distributed fileservers.
I thought the new idmapper was all about a more efficient way to talk between kernel and user space for id mapping. _________________ .sigs waste space and bandwidth |
|
Back to top |
|
|
wmark n00b
Joined: 28 Sep 2005 Posts: 17
|
Posted: Wed Feb 22, 2012 5:15 pm Post subject: |
|
|
depontius, you're right - I am wrong about the dependecy on NFSv4.1; the nfsidmap is the right USE-flag. Everything else should still be correct as long as I am not mistaken. Thanks!
Without the idmapper numerical UIDs/GIDs must match. But that configuration is prone to errors (syncing IDs, or utilizing NIS...), so I wouldn't deploy it in a network at home anymore. _________________ http://mark.ossdl.de/ |
|
Back to top |
|
|
depontius Advocate
Joined: 05 May 2004 Posts: 3509
|
Posted: Wed Feb 22, 2012 6:25 pm Post subject: |
|
|
wmark wrote: | Without the idmapper numerical UIDs/GIDs must match. But that configuration is prone to errors (syncing IDs, or utilizing NIS...), so I wouldn't deploy it in a network at home anymore. |
You mean that I don't have to keep /etc/passwd and /etc/group in sync on my home network? That's been a royal pain in the neck, and I've been doing it for years! Does nfsv3 use the idmapper? _________________ .sigs waste space and bandwidth |
|
Back to top |
|
|
LinuxTom l33t
Joined: 26 Mar 2006 Posts: 798
|
Posted: Wed Feb 22, 2012 10:07 pm Post subject: |
|
|
wmark wrote: | If you're using the following |
This not work. HELP ME!! |
|
Back to top |
|
|
LinuxTom l33t
Joined: 26 Mar 2006 Posts: 798
|
Posted: Wed Feb 22, 2012 10:26 pm Post subject: |
|
|
How do I increase the debug level, if I do not even know if the /etc/request-key.conf is used? |
|
Back to top |
|
|
skwang Tux's lil' helper
Joined: 12 May 2004 Posts: 149 Location: Chicago, IL
|
Posted: Sat Apr 07, 2012 3:42 pm Post subject: |
|
|
I wanted to add my two cents to this thread because I had a similar problem, idmapd was not running and all my UID/GIDs were 4294967294 (2^32-2). I used the information in this thread to help me solve this problem.
My solution involved:
1. Make sure rpc.idmapd (/etc/init.d/rpc.idmapd) is running on both server and client. It was running on the server, but the I had to add it to the default runlevel on the client.
2. I set the Method to "static". This is because I do not use LDAP or NIS, so I wound up having to manually map the users I have.
I have posted the relevant lines from my /etc/idmapd.conf here
Code: | [General]
Verbosity = 3
Domain = achaeans.net
[Mapping]
Nobody-User = nobody
Nobody-Group = nobody
[Translation]
Method = static
[Static]
skwang@achaeans.net = skwang
m3user@achaeans.net = m3user
|
I should point out that I have reset the verbosity to zero now that I have a working NFS. Basically in the static section I map the usernames on the NFS share to the usernames in the client. These names happens to be the same because I built this system with NFSv3 a long time ago, and recently started using NFSv4. I hope this helps anyone with a similar problem as mine. |
|
Back to top |
|
|
|