06-25-2012
I found out what it was having issues with. Even though I am logged in as root in the container, the NFS server for some reason cannot authenticate it as root so it made it user "unknown" which gives it the ownership of "-2". I changed the dfstab on the NFS server to export and use uid "0" for anybody that it authenticates as "unknown". I consider this a work around for now.
10 More Discussions You Might Find Interesting
1. Red Hat
Hello,
I am running RHEL4 AS. /net/hostname is not always accessible. To solve the problem, I restart nfs, nfslock and portmap.
in /var/log/messages, I keep on receiving:
nfs_statfs: statfs error = 116
1] What does the above error mean?
2] any idea why portmap becomes dead?
thanks. (1 Reply)
Discussion started by: melanie_pfefer
1 Replies
2. Solaris
Dear all,
Kindly need your advice on swap issue on my container, SunOS 5.10.
We have allocated swap 20GB and memory 8 GB. We have some application installed on the container.
A few days ago we experienced a very slow system response...even for command like ls, df -k, etc..
I tried to... (8 Replies)
Discussion started by: sprout009
8 Replies
3. Red Hat
Hi,
I am facing issue on NFS.
I have shared /data file file system on Server 192.192.192.1, added below lines in /etc/exports
/data 192.192.192.2(rw,no_root_squash,sync)
the owner of /data directory was test(uid 500)
and same I have mounted on another server 192.192.192.2 where the... (3 Replies)
Discussion started by: manoj.solaris
3 Replies
4. Solaris
Hi Guys.
Maybe someione can assist here.
Solaris 9 with a NFS mount point to a Netapp Filer.
NFS V3
Changes in the environment:
Moved from 1 building to a new one. (All the equipment and network stayed the same)
Errors:
nfs: NFS read failed for server netapp: error 11 (RPC: Server... (2 Replies)
Discussion started by: Boesman
2 Replies
5. UNIX for Dummies Questions & Answers
Hi whenever i execute ls -ltr i get following entry.
But there is no such user as 501 .What is the issue.
#ls -ltr
drwxrwxrwx 2 501 501 3896 Aug 19 10:46 File1
# cat /etc/passwd | grep 501
The problem is this folder is mouted on client machine using nfs.But after mouting client... (4 Replies)
Discussion started by: pinga123
4 Replies
6. Solaris
Hi All,
I have a problem as follows.
Historically, there was an Ultra10 workstation running Solaris 8 using automount to access NFS volumes on a Solaris 8 server.
The Ultra 10 was retired and the Solaris 8 server has been migrated to a Legacy Container (Solaris 8 Branded, whole root,... (9 Replies)
Discussion started by: hicksd8
9 Replies
7. Red Hat
Hi,
I have a conflict.
I have 2 servers: the 1st creates an application logs and the 2nd is an empty server.
I want to export (read-only) from the 1st server by NFS the directory that contains the logs to the 2nd server.
Now, the question is:
If in the 2nd server i'm doing a lot of... (3 Replies)
Discussion started by: moshesa
3 Replies
8. Red Hat
Hi Friends,
My source server is HP and my destination is linux. I have to mount a dir thru nfs from source to destn. almost 8 servers i did the same thing and it is working fine but on the 9th server i can't able to mount.
Everything i have did for nfs configuration.Even i can able to ping... (1 Reply)
Discussion started by: Mohamed Thamim
1 Replies
9. Red Hat
The server ip is 10.2.2.24. I have installed nfs-utils package the i have edited /etc/exports
i have added the following line
/home 10.2.2.0/24(rw,sync,no_root_squash,no_all_squash)
i have saved, i have started the nfs service, then i am trying to mount nfs sharing from client machine using... (5 Replies)
Discussion started by: ainstin
5 Replies
10. Red Hat
we are facing a weird NFS mount issue on one of the linux host , a NFS volume of 2.4TB is mounted in the linux host , but df only reports 131g , which exactly matches rootfilesytem size
nfs mount
filer_filer1:/vol/bug_test/q0
131G 116G 8.5G 94% /nas/bug_test
root... (2 Replies)
Discussion started by: skamal4u
2 Replies
nfs(7) Miscellaneous Information Manual nfs(7)
NAME
nfs, NFS - network file system
DESCRIPTION
The Network File System (NFS) allows a client node to perform transparent file access over the network. By using NFS, a client node oper-
ates on files residing on a variety of servers and server architectures, and across a variety of operating systems. File access calls on
the client (such as read requests) are converted to NFS protocol requests and sent to the server system over the network. The server
receives the request, performs the actual file system operation, and sends a response back to the client.
NFS operates in a stateless manner using remote procedure calls (RPC) built on top of an external data representation (XDR) protocol. The
RPC protocol enables version and authentication parameters to be exchanged for security over the network.
A server grants access to a specific file system to clients by adding an entry for that file system to the server's file.
A client gains access to that file system using the command to request a file handle for the file system (see mount(1M)). (A file handle
is the means by which NFS identifies remote files.) Once a client mounts the file system, the server issues a file handle to the client
for each file (or directory) the client accesses. If the file is removed on the server side, the file handle becomes stale (dissociated
with a known file), and the server returns an error with set to
A server can also be a client with respect to file systems it has mounted over the network; however, its clients cannot directly access
those file systems. If a client attempts to mount a file system for which the server is an NFS client, the server returns with set to The
client must mount the file system directly from the server on which the file system resides.
The user ID and group ID mappings must be the same between client and server. However, the server maps UID 0 (the superuser) to UID -2
before performing access checks for a client. This process prevents gaining superuser privileges on remote file systems.
RETURN VALUE
Generally, physical disk I/O errors detected at the server are returned to the client for action. If the server is down or inaccessible,
the client receives the message:
where is the hostname of the NFS server. The client continues resending the request until it receives an acknowledgement from the server.
Therefore, the server can crash or power down, and come back up without any special action required by the client. The client process
requesting the I/O will block, but remains sensitive to signals (unless mounted with the option) until the server recovers. However, if
mounted with the option, the client process returns an error instead of waiting indefinitely.
AUTHOR
was developed by Sun Microsystems, Inc.
SEE ALSO
exportfs(1M), share(1M), mount(1M), mount_nfs(1M), nfsd(1M), mount(2), fstab(4), dfstab(4).
nfs(7)