NFS filesystems not mounting at boot - can mount manually

Rick Stevens rstevens at vitalstream.com
Tue Nov 28 02:14:37 UTC 2006


On Mon, 2006-11-27 at 15:38 -0500, Thomas B. Walter wrote:
> Good Afternoon,
> 
> I have a lab of Dells running RHEL4u4. All but one NFS file systems are 
> not mounting automatically at boot. If I manually issue command "mount -a" the 
> offending file systems mount with no problems.
> 
> Contents of /etc/fstab:
> everest:/scratch        /scratch nfs   soft,bg     0  0
> yoda:/data/yoda/a         /data/yoda/a         nfs     soft,bg
> yoda:/data/yoda/b         /data/yoda/b         nfs     soft,bg
> 
> 
> Result of df -k command:
> [root at cslab2 log]# df -k
> Filesystem           1K-blocks      Used Available Use% Mounted on
> /dev/mapper/VolGroup00-LogVol00
>                        74730664   6816748  64117744  10% /
> /dev/sdb1               101086     12734     83133  14% /boot
> none                    516592         0    516592   0% /dev/shm
> everest:/scratch      17413280  12970784   4268384  76% /scratch
> 
> Relevent lines from /var/log/messages:
> Nov 27 15:08:23 cslab2 network: Bringing up interface eth0:  succeeded
> Nov 27 15:08:30 cslab2 mount: mount: backgrounding "everest:/scratch"
> Nov 27 15:08:36 cslab2 mount: mount: mount to NFS server 'everest' failed:
> Nov 27 15:08:36 cslab2 mount: mount: backgrounding "yoda:/data/yoda/a"
> Nov 27 15:08:36 cslab2 mount: mount: backgrounding "yoda:/data/yoda/b"
> Nov 27 15:08:36 cslab2 mount: System Error: No route to host(retrying).
> Nov 27 15:08:36 cslab2 netfs: Mounting NFS filesystems:  succeeded
> Nov 27 15:08:36 cslab2 netfs: Mounting other filesystems:  succeeded
> Nov 27 15:08:36 cslab2 kernel: i2c /dev entries driver
> 
> 
> Both yoda and everest have entries in /etc/hosts.
> 
> I see System Error: No route to host(retrying) but I don't know why one 
> NFS file system mounts and not the others.

Are both everest and yoda on the same network and/or NIC?  It may be
that one network or NIC's route isn't up by the time the "mount -a"
occurs, so you get the "no route to host" issue.

----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens at vitalstream.com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-   You possess a mind not merely twisted, but actually sprained.    -
----------------------------------------------------------------------




More information about the Redhat-install-list mailing list