Sponsored Content
Full Discussion: HP9000 Container - NFS Issue
Operating Systems HP-UX HP9000 Container - NFS Issue Post 302661785 by dardan on Monday 25th of June 2012 06:51:47 PM
Old 06-25-2012
i think first you should correct permissions on hp-ux for /var/adm/crash.
 

10 More Discussions You Might Find Interesting

1. Red Hat

nfs issue

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

Swap issue on Container

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

NFS Access Issue

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

New Member with NFS Issue

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

nfs issue.

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

NFS server on Legacy Container?

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

NFS Performance Issue

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

NFS mount issue

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

NFS mounting issue

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

NFS mount issue

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
mountd(8)						      System Manager's Manual							 mountd(8)

NAME
mountd - Services remote NFS compatible mount requests SYNOPSIS
mountd [-d] [-i] [-n] [-s] [exportsfile] FLAGS
Verifies the Internet addresses of hosts that make mount and unmount requests. If a client's address cannot be translated into a host name by the gethostbyaddr() function and then translated back into the same Internet address by the gethostbyname() function, the request is rejected. This option requires the BIND service for Internet address resolution. It offers the highest level of security, especially when combined with the -i option. Turns on Internet address verification and domain checking. If you are running the BIND service, mountd verifies that a host making a mount or unmount request is in the server's domain. Allows non-root mount requests to be served. This should only be specified if there are clients such as PC's that require it. ULTRIX BSD is allowed non-root mount requests by default. Use the -n flag to allow non-root mount requests. Verifies the Internet address of hosts that make mount and unmount requests. If a client's address cannot be translated into a host name by the gethostbyaddr() function, the request is rejected. If you are running the BIND service, the BIND server is used to translate the address. If you are not, the /etc/hosts file is used. If the -i option is not used and a client's address cannot be translated, the address is converted to a string of the form xx.xx.xx.xx. This allows access to exported file systems that do not specify a list of allowed hostnames. The -i option is automatically enabled when either the -d or the -s option is specified. Turns on Internet address verification and subdomain checking. If you are running the BIND service, mountd verifies that a host making a mount or unmount request is in the server's domain or subdomain. DESCRIPTION
The mountd daemon is the server for NFS protocol mount requests from clients. The mountd daemon responds to requests from remote computer systems to mount directories. When it receives a SIGHUP signal, mountd rereads the exports file. If you are on an NFS client and want to have changes to the export options on existing NFS client mounts take effect immediately, issue the showmount -e command and specify the name of the host that is exporting the directory or file system (where the exports file is located). This ensures that NFS is aware of the export list and options. The optional exportsfile argument specifies an alternate location for the exports file. /etc/exports is the default. Note, NFS Version 2 can export partitions that are greater than 2 gigabytes. However, they appear as 2 gigabyte partitions when viewed from NFS clients. FILES
Specifies the command path Contains a list of directories that can be exported Contains a table of local file systems mounted by remote NFS clients Contains errors logged by the mountd daemon RELATED INFORMATION
Commands: nfsstat(8), nfsd(8), portmap(8), showmount(8) Files: exports(4), mountdtab(4) delim off mountd(8)
All times are GMT -4. The time now is 12:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy