Mounting nfs from solaris client on linux server

Discussion in 'Linux Networking' started by Thomas Richter, Aug 4, 2007.

  1. Hi folks,

    I'm having a lot of trouble mounting an NFS share on a solaris machine
    (SunOs 5.10) that has been exported on a SuSE 10.2 linux. Probably
    someone has a smart idea:

    On the server side (linux), we have:

    # cat /etc/exportfs:

    latraviata:/home/thor # cat /etc/exports
    Importing Net File System (NFS) done
    latraviata:/home/thor # cat /etc/exports
    # See the exports(5) manpage for a description of the syntax of this file.
    # This file contains a list of all directories that are to be exported to
    # other computers via NFS (Network File System).
    # This file used by rpc.nfsd and rpc.mountd. See their manpages for details
    # on how make changes in this file effective.

    /local_data/thor/store
    129.69.12.14(ro,subtree_check,nohide,insecure,insecure_locks)
    /local_data/thor/store moon(ro,subtree_check,nohide,insecure_locks)
    #/local_data/thor/store *(ro,subtree_check)
    #/ *(ro,subtree_check)

    # ls -ld /local_data/thor/store/
    drwxr-xr-x 42 thor root 1264 31. Jul 16:24 /local_data/thor/store/

    Thus, the directory exists and is accessible. I only want and need a
    read-only access on it, see the vfstab below.

    # exportfs
    /local_data/thor/store
    moon
    /local_data/thor/store
    129.69.12.14

    Directories are exported.

    Portmap and mountd are running:

    root 7322 1 0 17:06 ? 00:00:00 /usr/sbin/rpc.mountd
    nobody 7047 1 0 16:44 ? 00:00:00 /sbin/portmap

    # cat /etc/hosts.allow:

    portmap: 129.69.12.7
    portmap: 129.69.12.14
    mountd: 129.69.12.7
    mountd: 129.69.12.14
    rpc.mountd: 129.69.12.7
    rpc.mountd: 129.69.12.14
    rpc.nfsd: 129.69.12.7
    rpc.nfsd: 129.69.12.14

    This machine (server) is 129.69.12.7, the solaris (client) is 129.69.12.14.

    On the solaris machine, we have this in the vfstab:

    129.69.12.7:/local_data/thor/store - /local/store nfs
    - yes ro

    I can ping both ways, ssh both ways, etc. The network is fine.

    Then, if I run a

    # mount /local/store/
    nfs mount: 129.69.12.7:/local_data/thore/store: No such file or directory

    on the client (solaris) it won't let me on the linux server.

    I run wireshark (ethereal) on the linux server, get the RPC/NFS packets
    fine, but I do see the following:

    Network File System
    [Program Version: 4]
    [V4 Procedure: COMPOUND (1)]
    Tag: mount
    minorversion: 0
    Operations (count: 11)
    Opcode: PUTROOTFH (24)
    Opcode: GETFH (10)
    Opcode: LOOKUP (15)
    Filename: local_data
    Opcode: GETFH (10)
    Opcode: GETATTR (9)
    Opcode: LOOKUP (15)
    Filename: thor
    Opcode: GETFH (10)
    Opcode: GETATTR (9)
    Opcode: LOOKUP (15)
    Filename: store
    Opcode: GETFH (10)
    Opcode: GETATTR (9)


    Thus, apparently, solaris is trying to locate /local_data/thor/store,
    which, as you see above, is available.

    I get the following back from the server:

    Network File System
    [Program Version: 4]
    [V4 Procedure: COMPOUND (1)]
    Status: NFS4ERR_NOENT (2)
    Tag: secinfo
    Operations (count: 1)


    NOENT, i.e. "no such file or directory". What's this, please?
    "Tag: secinfo" does that mean anything to you?

    Any hints?

    Greetings,
    Thomas
     
    Thomas Richter, Aug 4, 2007
    #1
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.