First NFS entry in fstab not mounting at boot

[Chris Kloiber]

Although I am not familiar with nfsv4, for nfsv3 'defaults' could be a 
pretty major performance problem.

I typically use rw,hard,intr,rsize=8192,wsize=8192,

In this case you might even want to add _netdev.

_netdev
        The filesystem resides on a device that requires network access
        (used to prevent the system from attempting to mount these
        filesystems until the network has been enabled on the system).

-- 
Chris Kloiber


On 05/16/2010 04:43 PM, g wrote:
> BadMagic wrote:
> <snip>
>
>> Basically, whichever entry goes first, doesn't get mounted.
> <snip>
>> I can manually mount it after I've logged in like:
> <snip>
>> If I repeat the top entry like:
> <snip>
>
> are the drives are spun down and at rest when you first try to mount?
>
> 'man nfs' for timeout setting info in fstab.
>
>
> are you connecting thru a firewall?
> anything in firewall rules time related?
>
>
> i recall a similar problem being posted years back, mandrake or redhat
> related. google did not show with word selections i used. :(
>
>
>> No entries/errors are created in any log files to explain what's going on.
>
> boot w/o gui to enable your bootup messages to see what is happening.
>
> draw back is that partitions are not mounted sequentially so you will
> have to watch closely for errors.
>
>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6653 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20100517/ade4d481/attachment.bin