nfs.idmapd not being consulted? (different nobody:nobody uid:gid issue)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



[ I haven't found an answer to this - the usual nobody:nobody issues
appear to be domainname related and not in play here... ]

What are the conditions where rpc.idmapd should be queried on an NFS
client?  I have a few that appears to be completely ignored, resulting
in /home/* being presented as belonging to nobody:nobody.  The same
configuration is fine on other identically configured boxes.

On two identically configured boxes, the following:
    killall rpc.idmapd && rpc.idmapd -f -vvvv

shows queries during "ls -l /home" on box A, but nothing (ever) on box
B (which is the problematic box).

I have many details from an investigation a few weeks ago, but think
it's prudent to keep the initial email brief.

Here are some of those details:
    - 1 NFS server
    - 10 NFS clients
    - 6 (initially deployed boxes) list /home/* fine.
    - 4 (added later) have the nobody:nobody issue.
    - All CentOS 6.3 (64 bit)
    - All clients installed via same kickstart configs (w/ diff hostname)
    - All servers were reinstalled after the 4 newer nodes were added,
so they should be identical.
    - diff'ing /etc dirs from good vs bad boxes reveals nothing significant.


Thanks


--
Amrit
AIM: ThatComputerGuy
ICQ: 3173735
http://transamrit.net/
--
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


[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux