|
|
NFS nobody problem
Dear all,
Both (NFS server/client) are on Solaris 10 x86.
drwx-----x 5 nobody nobody 512 Jun 25 16:04 userA
The NFS client does not have any user account. So that the
UID and GID are re-mapped to nobody as above. It does not
happen on NFS server in which Solaris 8 installed. How can
I get the correct UID/GID using NFS mounting as below:
drwx-----x 5 123456 123 512 Jun 25 16:04 userA
Thank you very much.
--
Johnson Chow
|
|
0
|
|
|
|
Reply
|
Mr
|
8/6/2009 5:48:56 AM |
|
On 2009-08-06 06:48:56 +0100, "Mr. Chow Wing Siu"
<wschow@Comp.HKBU.Edu.HK> said:
> Dear all,
>
> Both (NFS server/client) are on Solaris 10 x86.
>
> drwx-----x 5 nobody nobody 512 Jun 25 16:04 userA
>
> The NFS client does not have any user account. So that the
> UID and GID are re-mapped to nobody as above. It does not
> happen on NFS server in which Solaris 8 installed. How can
> I get the correct UID/GID using NFS mounting as below:
>
> drwx-----x 5 123456 123 512 Jun 25 16:04 userA
>
> Thank you very much.
It sounds like they're using NFSv4, and have different NFSv4 domains.
Make the domains the same, or force them to negotiate NFSv3. Both
things can be done by editing /etc/default/nfs.
--
Chris
|
|
0
|
|
|
|
Reply
|
Chris
|
8/6/2009 5:51:25 AM
|
|
Chris Ridd <chrisridd@mac.com> wrote:
> It sounds like they're using NFSv4, and have different NFSv4 domains.
> Make the domains the same, or force them to negotiate NFSv3. Both
> things can be done by editing /etc/default/nfs.
----------------------------------------
I just tried to set /etc/default/nfs :
NFSMAPID_DOMAIN=something.somewhere
and reboot in another set of NFS server/client.
There's no effect. Should I change to NFSv3? How?
--
Johnson Chow
|
|
0
|
|
|
|
Reply
|
Mr
|
8/6/2009 7:03:04 AM
|
|
Mr. Chow Wing Siu wrote:
> Chris Ridd <chrisridd@mac.com> wrote:
>> It sounds like they're using NFSv4, and have different NFSv4 domains.
>> Make the domains the same, or force them to negotiate NFSv3. Both
>> things can be done by editing /etc/default/nfs.
> ----------------------------------------
>
> I just tried to set /etc/default/nfs :
> NFSMAPID_DOMAIN=something.somewhere
>
> and reboot in another set of NFS server/client.
>
> There's no effect. Should I change to NFSv3? How?
>
Did you restart the NFS service on the server?
Do the client and server have the same domain name?
See the description of setting NFSMAPID_DOMAIN in the nfs man page.
--
Ian Collins
|
|
0
|
|
|
|
Reply
|
Ian
|
8/6/2009 8:19:11 AM
|
|
Ian Collins <ian-news@hotmail.com> wrote:
> Did you restart the NFS service on the server?
> Do the client and server have the same domain name?
> See the description of setting NFSMAPID_DOMAIN in the nfs man page.
------------------------------
1. I had tried either init 6 or svcadm restart nfs/server .
2. Same domain name and NFSMAPID_DOMAIN both in NFS server/client.
3. I use "mount -o vers=3" to fix this problem. However,
I think that NFSv4 client is better. Anyone has solution.
--
Johnson Chow
|
|
0
|
|
|
|
Reply
|
Mr
|
8/6/2009 10:29:30 AM
|
|
"Mr. Chow Wing Siu" <wschow@Comp.HKBU.Edu.HK> writes:
Hi,
> Ian Collins <ian-news@hotmail.com> wrote:
> > Did you restart the NFS service on the server?
> > Do the client and server have the same domain name?
> > See the description of setting NFSMAPID_DOMAIN in the nfs man page.
> ------------------------------
> 1. I had tried either init 6 or svcadm restart nfs/server .
> 2. Same domain name and NFSMAPID_DOMAIN both in NFS server/client.
> 3. I use "mount -o vers=3" to fix this problem. However,
> I think that NFSv4 client is better. Anyone has solution.
To have properly mapped credentials both client and server must be
able to resolve all involved user and group names (of course the NFSv4
domain names must also match). NFSv4 communicates user and group
information using strings (like "username@nfsv4domainname" and such).
NFSv3 uses numerical user/group IDs.
Client and server must be able to translate these "username@domain"
strings into numerical IDs and numerical IDs into "username@domain"
like strings. The numerical IDs don't need to be the same on
client and server though.
Ronald
--
* The whole problem with the world is that fools and fanatics are always
* so certain of themselves, but wiser people so full of doubts.
* --Bertrand Russell
|
|
0
|
|
|
|
Reply
|
Ronald
|
8/6/2009 7:30:22 PM
|
|
|
5 Replies
2971 Views
(page loaded in 0.082 seconds)
Similiar Articles: NFS nobody problem - comp.unix.solarisDear all, Both (NFS server/client) are on Solaris 10 x86. drwx-----x 5 nobody nobody 512 Jun 25 16:04 userA The NFS client does not have ... nfs problem - comp.sys.hp.hpuxNFS nobody problem - comp.unix.solaris Dear all, Both (NFS server/client) are on Solaris 10 x86. drwx-----x 5 nobody nobody 512 Jun 25 16:04 userA The NFS client does not ... nfs connection/version problem - comp.unix.solarisNFS nobody problem - comp.unix.solaris Dear all, Both (NFS server/client) are on Solaris 10 x86. drwx-----x 5 nobody nobody 512 Jun 25 16:04 userA The NFS client does not ... NFS mount problem - comp.unix.solarisNFS nobody problem - comp.unix.solaris NFS mount problem - comp.unix.solaris NFS nobody problem - comp.unix.solaris... nobody been on the system, and the ... to make ... Solaris 10 NFS 4 Problem - comp.unix.solarisNFS nobody problem - comp.unix.solaris Dear all, Both (NFS server/client) are on Solaris 10 x86. drwx-----x 5 nobody ... The Network File System ... locking problems ... NFS server and File locking problem - comp.unix.solarisNFS nobody problem - comp.unix.solaris NFS server and File locking problem - comp.unix.solaris NFS Server access list - comp.sys.sun.admin Nobody Nobody permissions. ... NFS Client hangs on "ls" and other access - comp.unix.solaris ...NFS Server access list - comp.sys.sun.admin NFS nobody problem - comp.unix.solaris Dear all, Both (NFS server/client) are on ... NFS Client hangs on "ls" and other access ... mountd - No default domain - comp.unix.solarisNFS nobody problem - comp.unix.solaris mountd - No default domain - comp.unix.solaris... have the same NFSv4 domain name, or users will find their files owned by 'nobody'. ... Account problem Solaris 8 - comp.sys.sun.adminNFS nobody problem - comp.unix.solaris It does not happen on NFS server in which Solaris 8 ... The NFS client does not have any user account. So ... NFS nobody problem ... NFS mounts not largefiles by default? - comp.unix.solaris ...NFS nobody problem - comp.unix.solaris Both things can be done by editing /etc/default/nfs. -- Chris ... Had nobody been on the system, and the ... to make remote mounts ... NFS nobody problem - comp.unix.solaris | Computer GroupDear all, Both (NFS server/client) are on Solaris 10 x86. drwx-----x 5 nobody nobody 512 Jun 25 16:04 userA The NFS client does not have ... Centos, Amazon Linux, NFS and the dreaded "nobody" problem ...I have been fighting a problem with mounting volumes from an NFS Server in AWS for a few days. With more pressing issues at hand, I had to try and google for ... 7/19/2012 6:42:19 PM
|
|
|
|
|
|
|
|
|