Sponsored Content
Top Forums UNIX for Dummies Questions & Answers NFS SERVER.....not responding Post 11600 by Perderabo on Saturday 8th of December 2001 12:03:51 PM
Old 12-08-2001
This sounds like an automounter problem. If you are not using the automounter, turn it off. You can do that by editing /etc/rc.config.d/nfsconf. Change "AUTOMOUNT=1" to "AUTOMOUNT=0" and reboot.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Solaris 9 server not responding

I'm in panic mode. This isn't a production server, however, is very vital to office. Sun V240 with Solaris 9, stopped accepting ftp sessions. When I tried to remote into box, it didn't respond. I have tried rebooting to boot in single user mode, no luck. I can see that it is ON but I can't get it... (3 Replies)
Discussion started by: mkeis1144
3 Replies

2. Solaris

Locate NFS "not responding still trying" application on client

At times I have unknown applications that hang for long periods of time over and over again after a network glitch. These are sometimes nfs4 but usually nfs3 clients and are always solaris10 systems. nfs: NFS server hostname not responding still trying nfs: NFS server hostname ok nfs: NFS... (1 Reply)
Discussion started by: HPAVC
1 Replies

3. Solaris

Solaris 9 as a nfs client -- centos as a nfs server.

Hello, I have a centos as nfs server, its name is centos_A. After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/* But, My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies

4. UNIX for Advanced & Expert Users

NFS server <servername> not responding still trying

Hi gurus, OS = SunOS 5.8 Not sure whether to post this in the scripting one or to advance and experts. Am posting on both since there is two things that am wanting to achieve. Am currerntly having NFS server errors below. At this stage, I am not sure whether I am having a SAN storage issue... (2 Replies)
Discussion started by: newbie_01
2 Replies

5. Red Hat

After umount -lf: kernel: nfs: server HOSTNAME not responding, timed out

Greetings! I'm testing a failover solution for NFSv4 on RHEL6 with latest updates. My script umounts (umount -lf /share) the faulty NFS share if it sees that's hanging on the client (the NFS daemon is down on the NFS server) and it mounts the share from another healthy NFS server. Sometimes... (4 Replies)
Discussion started by: Arsene Lupen
4 Replies

6. Red Hat

RHEL5 Server not responding

I have RHEL5 server Sometimes ping timeout occured and i can not access server from any tool or ILOM Any ideas how to solve this? (5 Replies)
Discussion started by: rafat_nasar2010
5 Replies

7. UNIX for Dummies Questions & Answers

Server with OpenVZ virtualisation is not responding but VMs are OK

Server is accessible only via IPMI. SSH and web control panel is timeout. Takes several hours. Server dont have high load or suspicious processes. I checked /etc/hosts.deny and restarted ssh, but nothing :( (0 Replies)
Discussion started by: postcd
0 Replies

8. AIX

AIX NFS Server and NFS Client

Hi 2 ALL, try to run NFS Server in AIX 7.1 : 1. Step by step on NFS Server node mkdir /tmp/test chgrp staff /tmp/test chmod 775 /tmp/test-- create export directory (fs) mknfsexp -d /tmp/test -t ro exportfs -va show mount -e :/# exportfs -av exports: 1831-187 re-exported /tmp/test... (4 Replies)
Discussion started by: penchev
4 Replies

9. UNIX for Beginners Questions & Answers

NFS server xxxxx not responding still trying

Hello, I got the below error on my AIX system when doing a df command NFS server xxx not responding still trying We check and know that the NFS server is not available anymore. So we would like to unmount it, but no help. / > umount /mountpoint/ umount: Could not find anything to... (4 Replies)
Discussion started by: Phat
4 Replies
SYSTEMD.AUTOMOUNT(5)                                             systemd.automount                                            SYSTEMD.AUTOMOUNT(5)

NAME
systemd.automount - Automount unit configuration SYNOPSIS
automount.automount DESCRIPTION
A unit configuration file whose name ends in ".automount" encodes information about a file system automount point controlled and supervised by systemd. This man page lists the configuration options specific to this unit type. See systemd.unit(5) for the common options of all unit configuration files. The common configuration items are configured in the generic [Unit] and [Install] sections. The automount specific configuration options are configured in the [Automount] section. Automount units must be named after the automount directories they control. Example: the automount point /home/lennart must be configured in a unit file home-lennart.automount. For details about the escaping logic used to convert a file system path to a unit name see systemd.unit(5). Note that automount units cannot be templated, nor is it possible to add multiple names to an automount unit by creating additional symlinks to its unit file. For each automount unit file a matching mount unit file (see systemd.mount(5) for details) must exist which is activated when the automount path is accessed. Example: if an automount unit home-lennart.automount is active and the user accesses /home/lennart the mount unit home-lennart.mount will be activated. Automount units may be used to implement on-demand mounting as well as parallelized mounting of file systems. IMPLICIT DEPENDENCIES
The following dependencies are implicitly added: o If an automount unit is beneath another mount unit in the file system hierarchy, both a requirement and an ordering dependency between both units are created automatically. o An implicit Before= dependency is created between an automount unit and the mount unit it activates. DEFAULT DEPENDENCIES
The following dependencies are added unless DefaultDependencies=no is set: o Automount units acquire automatic Before= and Conflicts= on umount.target in order to be stopped during shutdown. FSTAB
Automount units may either be configured via unit files, or via /etc/fstab (see fstab(5) for details). For details how systemd parses /etc/fstab see systemd.mount(5). If an automount point is configured in both /etc/fstab and a unit file, the configuration in the latter takes precedence. OPTIONS
Automount files must include an [Automount] section, which carries information about the file system automount points it supervises. The options specific to the [Automount] section of automount units are the following: Where= Takes an absolute path of a directory of the automount point. If the automount point does not exist at time that the automount point is installed, it is created. This string must be reflected in the unit filename. (See above.) This option is mandatory. DirectoryMode= Directories of automount points (and any parent directories) are automatically created if needed. This option specifies the file system access mode used when creating these directories. Takes an access mode in octal notation. Defaults to 0755. TimeoutIdleSec= Configures an idle timeout. Once the mount has been idle for the specified time, systemd will attempt to unmount. Takes a unit-less value in seconds, or a time span value such as "5min 20s". Pass 0 to disable the timeout logic. The timeout is disabled by default. SEE ALSO
systemd(1), systemctl(1), systemd.unit(5), systemd.mount(5), mount(8), automount(8), systemd.directives(7) systemd 237 SYSTEMD.AUTOMOUNT(5)
All times are GMT -4. The time now is 12:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy