Results 1 to 3 of 3

Thread: [nfs] can't no more mount nfs file system from 13.2 client

  1. #1
    Join Date
    May 2009
    Location
    Liège Walifornia
    Posts
    490

    Default [nfs] can't no more mount nfs file system from 13.2 client

    Greetings !!
    It worked this morning... and now the 13.2 client can not mount the NFS file systems it has mounted a lot of times.

    My server uses the tcp port 4000 and 4001 as mount port

    Client config -- /etc/fstab

    Code:
    # NFS mount(s)
    
    192.168.0.3:/windows/Ntfs1            /datas1/nfsshares/Ntfs1   nfs defaults 0 0
    192.168.0.3:/windows/Ntfs2            /datas1/nfsshares/Ntfs2   nfs defaults 0 0
    192.168.0.3:/windows/Datas1         /datas1/nfsshares/Datas1  nfs defaults 0 0
    192.168.0.3:/windows/Datas2         /datas1/nfsshares/Datas2  nfs defaults 0 0
    192.168.0.3:/windows/Datas3         /datas1/nfsshares/Datas3  nfs defaults 0 0
    192.168.0.3:/windows/Linux            /datas1/nfsshares/Linux   nfs defaults 0 0
    192.168.0.3:/windows/System         /datas1/nfsshares/System  nfs defaults 0 0
    Server config -- /etc/exports

    Code:
    /nfsshares/ntfs1    *(crossmnt,rw,no_root_squash)
    /nfsshares/ntfs2    *(crossmnt,rw,no_root_squash)
    /nfsshares/Datas1    *(crossmnt,rw,no_root_squash)
    /nfsshares/Datas2    *(crossmnt,rw,no_root_squash)
    /nfsshares/Datas3    *(crossmnt,rw,no_root_squash)
    /nfsshares/Linux    *(crossmnt,rw,no_root_squash)
    /nfsshares/System    *(crossmnt,rw,no_root_squash)
    At the client side:

    When trying to mount using mount.nfs or mount.nfs4 I got timeout.
    showmount -e 192.168.0.3 got timeout.

    rpcinfo -p gives

    Code:
       
    program vers proto   port  service
        100000    4   udp    111  portmapper
        100000    3   udp    111  portmapper
        100000    2   udp    111  portmapper
        100000    4   tcp    111  portmapper
        100000    3   tcp    111  portmapper
        100000    2   tcp    111  portmapper


    At the server side:

    rpcinfo -s gives
    Code:
       program version(s) netid(s)                         service     owner
        100000  2,3,4     local,udp,tcp,udp6,tcp6          portmapper  superuser
        100024  1         tcp6,udp6,tcp,udp                status      103
        100005  3,2,1     tcp6,udp6,tcp,udp                mountd      superuser
        100003  4,3       udp6,tcp6,udp,tcp                nfs         superuser
        100227  3         udp6,tcp6,udp,tcp                nfs_acl     superuser
        100021  4,3,1     tcp6,udp6,tcp,udp                nlockmgr    superuser
    rpcinfo -p gives

    Code:
     
    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  40561  status
        100024    1   tcp  50935  status
        100005    1   udp   4001  mountd
        100005    1   tcp   4001  mountd
        100005    2   udp   4001  mountd
        100005    2   tcp   4001  mountd
        100005    3   udp   4001  mountd
        100005    3   tcp   4001  mountd
        100003    3   tcp   4000  nfs
        100003    4   tcp   4000  nfs
        100227    3   tcp   4000  nfs_acl
        100003    3   udp   4000  nfs
        100003    4   udp   4000  nfs
        100227    3   udp   4000  nfs_acl
        100021    1   udp  56892  nlockmgr
        100021    3   udp  56892  nlockmgr
        100021    4   udp  56892  nlockmgr
        100021    1   tcp  39027  nlockmgr
        100021    3   tcp  39027  nlockmgr
        100021    4   tcp  39027  nlockmgr
    Questions:

    What happened ? How does the NFS stopped working ?

    How can I set the NFS working again ? As I did not changed anything since this morning.


    ADD: with firewall off it works :{

    I had set the 4000 port and 4001 port (tcp) opened.












    Last edited by soundlord; 08-Nov-2017 at 14:10. Reason: adding informations

  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,670
    Blog Entries
    3

    Default Re: [nfs] can't no more mount nfs file system from 13.2 client

    I'm currently not having problems.

    There was a firewall update today. I noticed a bug report - Bug 1067057

    Hmm, reading that report, I see:
    "For openSUSE this means Leap 42.2 is affected but 42.3 is not."
    I guess that's why you are seeing the problem, and I am not.

    I suggest reading the bug report. Alternatively, you could turn off the firewall until this is resolved. That would be the firewall on your 42.2 server.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  3. #3
    Join Date
    May 2009
    Location
    Liège Walifornia
    Posts
    490

    Default Re: [nfs] can't no more mount nfs file system from 13.2 client

    I just got back from work. Yesterday I went to the zypper logs and saw opensuse firewall 2 was updated (I do automatic updates)

    Yesterday I solved the issue by manually opening the port 111 using iptables.

    thanks for the help !!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •