Sponsored Content
Operating Systems Solaris NFS mounts not automounting on boot Post 302961787 by os2mac on Thursday 3rd of December 2015 03:38:37 PM
Old 12-03-2015
thanks got that...

Code:
netapp:/nfs_tst_06a/informtca   -       /infrmtca/informtca     nfs -   yes hard,nosuid,nodevices,intr,proto=tcp,vers=3,rsize=32768,wsize=32768
netapp:/nfs_tst_06b/pssprtstg   -       /infrmtca/pssprtstg     nfs -   yes hard,nosuid,nodevices,intr,proto=tcp,vers=3,rsize=32768,wsize=32768
netapp:/nfs_tst_06c/infadcdev   -       /infrmtca/infadcdev     nfs -   yes hard,nosuid,nodevices,intr,proto=tcp,vers=3,rsize=32768,wsize=32768
netapp:/nfs_tst_06d/dev         -       /infrmtca/dev           nfs -   yes hard,nosuid,nodevices,intr,proto=tcp,vers=3,rsize=32768,wsize=32768
netapp:/nfs_tst_06e/tst         -       /infrmtca/tst           nfs -   yes hard,nosuid,nodevices,intr,proto=tcp,vers=3,rsize=32768,wsize=32768
netapp:/nfs_tst_06f/informatica -       /infrmtca/informatica   nfs -   yes hard,nosuid,nodevices,intr,proto=tcp,vers=3,rsize=32768,wsize=32768
netapp:/c181_shared/OF_users    -       /users                  nfs -   yes hard,nosuid,intr,vers=3,rsize=32768,wsize=32768
netapp:/nfs_test/app02          -       /test/app02             nfs -   yes hard,suid,intr,vers=3,rsize=32768,wsize=32768

 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Problem: Automounting Home directory for nis & nfs configuration doesn't work

Hi all, First of all, i am so sorry about my bad level in English writing. I have some problem in linux and i hope the experts of this forum to help me if they have enough time to reply to me. I have a scenario of configuring NIS and NFS in Redhat Linux environment such that user can login... (0 Replies)
Discussion started by: pioneer
0 Replies

2. AIX

NFS does not mount on boot!

Hi, Can someone help me on this? I'm not able to enable a well working mounting process for NFS filesystems on boot time. On the server side (AIX 5.2) everything seems to be OK and correctly exported, seeing other clients (AIX 5.2) are able to mount normally on boot time. On a client in... (5 Replies)
Discussion started by: padawan75
5 Replies

3. AIX

NFS mounts and user permissions

We need to allow ordinary users to preform NFS mounts on a AIX server without giving them root access to the server. Is there a way to give an ordinary users root access on a tem basis or a script to allow them to preform NFS mounts? (4 Replies)
Discussion started by: daveisme
4 Replies

4. AIX

AIX - boot - nfs problem

Hello Experts, I'm trying to boot my AIX server via network using another AIX as a boot server. I use tcpdump to monitor the process. After my boot client received .info file and mounted nfs resource (checked by 'showmount -a' from boot server) it hung. I noticed a lot of following entries: ... (0 Replies)
Discussion started by: jarekkk
0 Replies

5. Solaris

nfs export not working at boot

we have a Solaris 8 nfs server that exported two shares. entries are in /etc/dfs/dfstab. clients have been accessing these shares for several years. we just rebooted this nfs server and noticed that no share gets exported. I don't see relevant messages from dmsg nor messages file, is there... (6 Replies)
Discussion started by: jalite19
6 Replies

6. Solaris

Max. number of NFS mounts

Hi, I was wondering, whether there is a limit regarding the max number of nfs mounts in Oracle Solaris 10 (newest update). The data center plans to migrate from a fibre channel based storage environment (hitachi) to a nfs based storage environment (netapp). Regarding the Solaris 10 database... (1 Reply)
Discussion started by: schms
1 Replies

7. Shell Programming and Scripting

find command exclude nfs mounts

Gentleman and Ladies, I am having some difficulty in regards to the find utility. I am trying to not traverse nfs mounts when searching for files or directories. This command does not seem to work. It still returns directories that live on nfs shares. The man page says: -fstype type... (6 Replies)
Discussion started by: jaysunn
6 Replies

8. UNIX for Dummies Questions & Answers

NFS not mouting at boot

hi guys I have a server suse 11 two IP different segments one IP is point to point to NFS Storage. Administration IP: 10.7.10.100 NFS-Storage IP: 192.168.10.50 weird thing is I defined the NFS I can mount them using mount -a but when I reboot the server the NFS mount points are not there... (11 Replies)
Discussion started by: karlochacon
11 Replies

9. Red Hat

NFS mounts query

We have 2 servers in cluster. Node1 has an ext3 mount for backups and the other connects using NFS to this node1. I believe the reason it is configured in this manner is to not duplicate backups since this is a Database server. Not sure this was the reason though. Right now if node1 goes down all... (5 Replies)
Discussion started by: ikn3
5 Replies

10. AIX

Sysmirror 7.1.3 Resource Group NFS mounts

Hello all, I'm working to fix a two-node SysMirror cluster that uses NFS mounts from a NetApp appliance as the data repository. Currently all the NFS mounts/unmounts are called from the application controller scripts, and since file collection isn't currently working, (One fight at at time... (3 Replies)
Discussion started by: ZekesGarage
3 Replies
NFS(5)							     Linux Programmer's Manual							    NFS(5)

NAME
nfs - nfs fstab format and options SYNOPSIS
/etc/fstab DESCRIPTION
The fstab file contains information about which filesystems to mount where and with what options. For NFS mounts, it contains the server name and exported server directory to mount from, the local directory that is the mount point, and the NFS specific options that control the way the filesystem is mounted. Here is an example from an /etc/fstab file from an NFS mount. server:/usr/local/pub /pub nfs rsize=8192,wsize=8192,timeo=14,intr Options rsize=n The number of bytes NFS uses when reading files from an NFS server. The default value is dependent on the kernel, currently 1024 bytes. (However, throughput is improved greatly by asking for rsize=8192.) wsize=n The number of bytes NFS uses when writing files to an NFS server. The default value is dependent on the kernel, currently 1024 bytes. (However, throughput is improved greatly by asking for wsize=8192.) timeo=n The value in tenths of a second before sending the first retransmission after an RPC timeout. The default value is 7 tenths of a second. After the first timeout, the timeout is doubled after each successive timeout until a maximum timeout of 60 seconds is reached or the enough retransmissions have occured to cause a major timeout. Then, if the filesystem is hard mounted, each new timeout cascade restarts at twice the initial value of the previous cascade, again doubling at each retransmission. The maximum timeout is always 60 seconds. Better overall performance may be achieved by increasing the timeout when mounting on a busy network, to a slow server, or through several routers or gateways. retrans=n The number of minor timeouts and retransmissions that must occur before a major timeout occurs. The default is 3 timeouts. When a major timeout occurs, the file operation is either aborted or a "server not responding" message is printed on the console. acregmin=n The minimum time in seconds that attributes of a regular file should be cached before requesting fresh information from a server. The default is 3 seconds. acregmax=n The maximum time in seconds that attributes of a regular file can be cached before requesting fresh information from a server. The default is 60 seconds. acdirmin=n The minimum time in seconds that attributes of a directory should be cached before requesting fresh information from a server. The default is 30 seconds. acdirmax=n The maximum time in seconds that attributes of a directory can be cached before requesting fresh information from a server. The default is 60 seconds. actimeo=n Using actimeo sets all of acregmin, acregmax, acdirmin, and acdirmax to the same value. There is no default value. retry=n The number of minutes to retry an NFS mount operation in the foreground or background before giving up. The default value is 10000 minutes, which is roughly one week. namlen=n When an NFS server does not support version two of the RPC mount protocol, this option can be used to specify the maximum length of a filename that is supported on the remote filesystem. This is used to support the POSIX pathconf functions. The default is 255 characters. port=n The numeric value of the port to connect to the NFS server on. If the port number is 0 (the default) then query the remote host's portmapper for the port number to use. If the remote host's NFS daemon is not registered with its portmapper, the standard NFS port number 2049 is used instead. mountport=n The numeric value of the mountd port. mounthost=name The name of the host running mountd . mountprog=n Use an alternate RPC program number to contact the mount daemon on the remote host. This option is useful for hosts that can run multiple NFS servers. The default value is 100005 which is the standard RPC mount daemon program number. mountvers=n Use an alternate RPC version number to contact the mount daemon on the remote host. This option is useful for hosts that can run multiple NFS servers. The default value is version 1. nfsprog=n Use an alternate RPC program number to contact the NFS daemon on the remote host. This option is useful for hosts that can run multiple NFS servers. The default value is 100003 which is the standard RPC NFS daemon program number. nfsvers=n Use an alternate RPC version number to contact the NFS daemon on the remote host. This option is useful for hosts that can run multiple NFS servers. The default value is version 2. nolock Disable NFS locking. Do not start lockd. This has to be used with some old NFS servers that don't support locking. bg If the first NFS mount attempt times out, retry the mount in the background. After a mount operation is backgrounded, all subsequent mounts on the same NFS server will be backgrounded immediately, without first attempting the mount. A missing mount point is treated as a timeout, to allow for nested NFS mounts. fg If the first NFS mount attempt times out, retry the mount in the foreground. This is the complement of the bg option, and also the default behavior. soft If an NFS file operation has a major timeout then report an I/O error to the calling program. The default is to continue retrying NFS file operations indefinitely. hard If an NFS file operation has a major timeout then report "server not responding" on the console and continue retrying indef- initely. This is the default. intr If an NFS file operation has a major timeout and it is hard mounted, then allow signals to interupt the file operation and cause it to return EINTR to the calling program. The default is to not allow file operations to be interrupted. posix Mount the NFS filesystem using POSIX semantics. This allows an NFS filesystem to properly support the POSIX pathconf com- mand by querying the mount server for the maximum length of a filename. To do this, the remote host must support version two of the RPC mount protocol. Many NFS servers support only version one. nocto Suppress the retrieval of new attributes when creating a file. noac Disable all forms of attribute caching entirely. This extracts a server performance penalty but it allows two different NFS clients to get reasonable good results when both clients are actively writing to common filesystem on the server. tcp Mount the NFS filesystem using the TCP protocol instead of the default UDP protocol. Many NFS servers only support UDP. udp Mount the NFS filesystem using the UDP protocol. This is the default. All of the non-value options have corresponding nooption forms. For example, nointr means don't allow file operations to be interrupted. FILES
/etc/fstab SEE ALSO
fstab(5), mount(8), umount(8), exports(5) AUTHOR
"Rick Sladkey" <jrs@world.std.com> BUGS
The posix, and nocto options are parsed by mount but currently are silently ignored. The tcp and namlen options are implemented but are not currently supported by the Linux kernel. The umount command should notify the server when an NFS filesystem is unmounted. Linux 0.99 20 November 1993 NFS(5)
All times are GMT -4. The time now is 04:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy