Bug 6994

Summary: NFS share does not mount at boot but mounts with a root "mount -a" command
Product: Mageia Reporter: William Kenney <wilcal.int>
Component: InstallerAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Normal CC: DShelbyD
Version: Cauldron   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description William Kenney 2012-08-09 22:37:32 CEST 
NFS Client

Created /mnt/sherman folder

After boot if user attempts to access NFS share using dolphin I get the following error:

An error occurred while accessing '/home/wilcal/databank on 192.168.1.2', the system responded:
mount: only root can mount 192.168.1.2:/home/wilcal/databank on /mnt/sherman

In a su terminal if I run "mount -a" the nfs share mounts to /mnt/sherman
just fine and is read write accessible by the user.

/etc/fstab mount command looks like this and works just fine in M2.

192.168.1.2:/home/wilcal/databank /mnt/sherman nfs rsize=8192,wsize=8192,nosuid,soft 0 0

I think the nfs is fine maybe just a timing thing.
I added to  /etc/sysconfig/network-scripts/ifcfg-eth0  the line:
LINK_DETECTION_DELAY=5

but that didn't help. After su terminal mounting all works just fine.

I don't think this is related to:

https://bugs.mageia.org/show_bug.cgi?id=6918

Maybe the same as:

https://bugs.mageia.org/show_bug.cgi?id=6541
Comment 1 William Kenney 2012-09-11 20:16:40 CEST 
This bug is still valid for Mageia 3 Alpha 1
Comment 2 William Kenney 2012-10-15 17:39:25 CEST 
This bug is still valid for me in M3A2 on
10/15/12 using boot.iso 10/02/12 32-bit
Comment 3 David Deaderick 2012-11-30 16:27:49 CET 
This bug is valid for me in M3A3. The relevant fstab line is
192.168.1.2:/mnt/data /home/david/Server nfs defaults 0 0

It's a home server running NAS4Free.

The mount, configured manually in fstab, shows up in MCC (Network Sharing/Configure NFS Shares) but I have to tell it to mount after each reboot.

CC: (none) => DShelbyD

Comment 4 Manuel Hiebel 2012-11-30 18:00:04 CET 

*** This bug has been marked as a duplicate of bug 6541 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE