Link to home
Start Free TrialLog in
Avatar of cblazque
cblazque

asked on

nfs troubles with Red-Hat

I just installed Red-Hat (some of the last versions) and I'm trying to share
a file system and didnt´t work.

What I´ve found is:

1. by default the system was running
under 5 mode (inittab, I changed it to
3)

2. There´re some files missing in
/etc/rc.d like rc.M and other file
(which I don´t remember but it´s the one that loads all the rpc´s deamos like rpc.portmap,rpc.mountd, rpc.nfsd etc)

3. The file /usr/sbin/rpc.portmap is
missing too, I copied it from  a slackware version, but it didn´t work.

4. The /etc/exports file exists when the correct parameters

5. I´ve done this before (sharing a file system) in a slackware version.
with no problem, the system that is mounting the shared file system is a Ultra (Sun)

6. The Ultra machine is running the proper deamos to mount a nfs file
(nfs.client)

7. Is there another way to share file systems under Red-Hat?, because I´ve found that the files that makes this work in Slackware, they just don´t exist in Red-Hat

Is all this about a bad installation of
Red-Hat??????

Any idea,
Thanks in advance.....
ASKER CERTIFIED SOLUTION
Avatar of tmoss
tmoss

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of sane101999
sane101999

Some things vary significantly among Linux distributions, and the method for starting up daemons on boot is one of them.  Copying system files from one distribution to another is unlikely to help and likely to make your configuration very difficult to reproduce.

1.  Mode 5 is graphical login (vs. 3 for console login) and makes no difference to network configuration.

2.  /etc/rc.d on most Linux distributions (including any recent RedHat release) contains SysV-style init scripts.  RedHat provides a chkconfig utility (similar calling convention to IRIX chkconfig, but with different back-end behavior) for manipulating the symbolic links in /etc/rc.d/rc?.d, which control what startup / shutdown scripts are run during transitions from one init state to another.  

3.  The current RPC port mapper installs at /sbin/portmap.  It is part of the portmap RPM, which should be installed on your system (rpm -qi portmap).

4.  /etc/exports is indeed the NFS server configuration file.  It has SunOS 4.x-like syntax.

5.  Was your Slackware release using the kernel NFS server code?  NFS service has changed a lot since 1.2.x kernels.

Mostly you probably need to undo your copying of things from Slackware and run:

chkconfig portmap on
chkconfig nfs on
/etc/rc.d/init.d/portmap stop
/etc/rc.d/init.d/portmap start
/etc/rc.d/init.d/nfs start

nfs start will run exportfs -r, which should export everything in /etc/exports.  I have just tried this on a RedHat 6.0 box on which I have not previously run an NFS server, and it worked.

Hope this helps.

- Michael K. Edwards
  SANE.net, LLC
  (medwards@sane.net)
Having similar problems!

The ultra running solaris looks like this

mount linux:/jaz /mnt
mount: linux: NFS service not responding
mount: retrying: /mnt

then the system just hangs until a ctr<c> is issued.

the /var/log/messages contains:

Nov 3 10:22:37 linux kernel: svc: unknown version (3)

The jaz drive may be mounted from other unix machines on the network.