Bug 17931 - NFS mount function is not working
Summary: NFS mount function is not working
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Guillaume Rousse
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-09 22:22 CET by William Kenney
Modified: 2016-04-03 19:51 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description William Kenney 2016-03-09 22:22:39 CET
Description of problem:

Setting up an NFS mount, either manually or using the MCC
is not successful. I'll add more details to this as I
explore it some more. I'm using the same script line I use
in M5, /etc/fstab. nfs-utils is installed. Here's that command:

192.168.1.2:/home/mageia/distrib  /home/mageia/sherman_repo nfs rsize=8192,wsize=8192,nosuid,soft 0 0
Marja Van Waes 2016-03-12 20:23:00 CET

CC: (none) => marja11, nic

Comment 1 Nic Baxter 2016-03-13 08:34:32 CET
I got it to work by adding  nfsvers=4 to the mount options, nfsvers=3 works as well.
I am guessing that the handshake between client and server fails when the version is not explicit.
My server is mga5  with nfs-utils-1.3.0-6.mga5 and Linux albert.nicbaxter.home 4.1.15-desktop-2.mga5 #1 SMP Wed Jan 20 17:05:51 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

The client is Mageia-6-dev1-x86_64-DVD.iso (Fri Mar 11 13:49:02 CET 2016) with nfs-utils-1.3.3-3.mga6  and Linux localhost 4.4.4-desktop-1.mga6 #1 SMP Sat Mar 5 11:33:53 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

The server is showing
rpcinfo -p 192.168.3.50
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  52562  status
    100024    1   tcp  47917  status
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    3   tcp   2049  nfs_acl
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100227    3   udp   2049  nfs_acl
    100021    1   udp  41790  nlockmgr
    100021    3   udp  41790  nlockmgr
    100021    4   udp  41790  nlockmgr
    100021    1   tcp  46646  nlockmgr
    100021    3   tcp  46646  nlockmgr
    100021    4   tcp  46646  nlockmgr
    100005    1   udp  44474  mountd
    100005    1   tcp  57901  mountd
    100011    1   udp    911  rquotad
    100005    2   udp  35870  mountd
    100011    2   udp    911  rquotad
    100005    2   tcp  54516  mountd
    100011    1   tcp    911  rquotad
    100011    2   tcp    911  rquotad
    100005    3   udp  37259  mountd                                                                                             
    100005    3   tcp  40623  mountd

Assignee: bugsquad => guillomovitch

Comment 2 William Kenney 2016-04-03 19:51:26 CEST
I'm gonna take this one off the table for now as it seems to be working now.

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


Note You need to log in before you can comment on or make changes to this bug.