Solved

Error attempting to auto mount /home directories to an NFS server under RedHat

Posted on 2007-03-21
7
660 Views
Last Modified: 2013-12-16
Hi All,

I'm currently using RedHat 4 Enterprise Workstation 4 U4 for a small lab.

I've got a Fedora Core 6 File Server with an NFS share, and I'm simply exporting the /home directory on that server for the RH4Ent clients to auto.home their /home directories.

When I restart autofs I get:

failed to load map: "/usr/sbin/automount --timeout=60 /home[WARNING]c/auto.home"

So it will not automount the /home directory.

On the server I'm simply using corresponding users and groups.  In a test environment using all Fedora Core machines, it works without an issue.

Also, if I issue the command:

[root@tuw5 etc]# mount lfs1:/home /home/

It works without a problem and the NFS share on the LFS1 server is mounted to the local RedHat Ent 4 workstation.

What am I doing wrong?



Here are the files:

[root@tuw5 etc]# more auto.master
#
# $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $
#
# Sample auto.master file
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# For details of the format look at autofs(5).
#/misc  /etc/auto.misc --timeout=60
/misc   /etc/auto.misc
#/net   /etc/auto.net
/net    -hosts
/home   /etc/auto.home --timeout 300

[root@tuw5 etc]# more auto.home
* -fstype=nfs,soft,intr,rsize=8192,wsize=8192,nosuid,tcp lfs1:/home:&

0
Comment
Question by:gerhardub
  • 4
  • 3
7 Comments
 
LVL 38

Accepted Solution

by:
wesly_chen earned 500 total points
ID: 18767051
> [root@tuw5 etc]# more auto.home
> * -fstype=nfs,soft,intr,rsize=8192,wsize=8192,nosuid,tcp lfs1:/home:&
change to
* -fstype=nfs,soft,intr,rsize=8192,wsize=8192,nosuid,tcp lfs1:/home/&

Besides, check your /etc/sysconfig/autofs and edit two options
--- /etc/sysconfig/autofs ---
LOCALOPTIONS="soft,intr,rsize=8192,wsize=8192,nosuid,tcp"
DAEMONOPTIONS="--timeout=300"
-------
Then you can change to /etc/auto.home
*  lfs1:/home/&
0
 
LVL 1

Author Comment

by:gerhardub
ID: 18767627
Thanks, I'll give that a try and tell you if it appears to work!!

Is this a syntax issue between RedHat and Fedora?
0
 
LVL 38

Expert Comment

by:wesly_chen
ID: 18767701
> Is this a syntax issue between RedHat and Fedora?
No, but there are some options difference for autofs in /etc/sysconfig/autofs since there is new feature update in autofs recently.
0
Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

 
LVL 1

Author Comment

by:gerhardub
ID: 18769002
Yeah, it was syntax based, I guess due to version, which is confusing.

Fedora Core 6 (which has a newer Kernel than RH Ent WS4 U4) uses:

* lfs1:/home /home:&

RedHat 4WS U4 uses:

* lfs1:/home /home/&

..and that appears to have been the issue.
0
 
LVL 1

Author Comment

by:gerhardub
ID: 18770661
Well, I'm still getting an error when I attempt to get RedHat to load the auto.home settings...

I'm going to open another ticket for this.  It works flawlessly on a new RedHat installation, so what is preventing this one from working?

The new case is here:

http://www.experts-exchange.com/OS/Linux/Q_22465459.html
0
 
LVL 38

Expert Comment

by:wesly_chen
ID: 18773562
> Fedora Core 6 (which has a newer Kernel than RH Ent WS4 U4) uses:
> * lfs1:/home /home:&
Mmm, I will try it on RHEL5 (based on FC6) to see if there is issue over there or not.
0
 
LVL 1

Author Comment

by:gerhardub
ID: 18775137
When I say "new" installation, I mean taking that last release of RH 4 Wks Ent U4 and isntalling that freash.  I then use one of the RH systems for the NFS server, and connect to it with the other.

Since I'm going from Fedora Core 6 (32bit) to RH 4 U4 (x86_64), I wonder if there is an incompatibility?

I wonder if they support the same versions of NFS, etc...
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Daily system administration tasks often require administrators to connect remote systems. But allowing these remote systems to accept passwords makes these systems vulnerable to the risk of brute-force password guessing attacks. Furthermore there ar…
It’s 2016. Password authentication should be dead — or at least close to dying. But, unfortunately, it has not traversed Quagga stage yet. Using password authentication is like laundering hotel guest linens with a washboard — it’s Passé.
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now