Help: NFS mouting issue, Ctrl+C, bad directory - SUN

This is a discussion on Help: NFS mouting issue, Ctrl+C, bad directory - SUN ; Hi all, I have to post it again to get further assistance on NFS mapping, as this is second time this month it happened The situation is that both servers are running solaris, A (client) is on 5.10, B (server)is ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Help: NFS mouting issue, Ctrl+C, bad directory

  1. Help: NFS mouting issue, Ctrl+C, bad directory

    Hi all,

    I have to post it again to get further assistance on NFS mapping, as this is
    second time this month it happened

    The situation is that both servers are running solaris, A (client) is on
    5.10, B (server)is on 5.9.

    A can mount any other server (windows or Unix) fine, but not B,

    And B has no problem mounting other file system.

    umount -f
    didn't work, it just sit there and doing nothing, I have to do ctrl+c to
    quit, then I got "bad directory" message.

    so the only option for me is to reboot to get it fixed.

    During my diagnose, I found it is interested or maybe I am wrong.

    disabled May_02 svc:/network/nfs/server:default
    online May_02 svc:/network/nfs/cbd:default
    online May_02 svc:/network/nfs/mapid:default
    online May_02 svc:/network/nfs/status:default
    online May_02 svc:/network/nfs/nlockmgr:default
    online May_02 svc:/network/nfs/client:default
    online May_08 svc:/network/nfs/rquota:default



    I disable all of them, does that mean that I can't mount any other server
    because services have been disable?

    If this is the true, it is funny, because I can still access to other
    server's exported file system.


    Please give me some tips



  2. Re: Help: NFS mouting issue, Ctrl+C, bad directory

    steeles wrote:
    > Hi all,
    >
    > I have to post it again to get further assistance on NFS mapping, as this is
    > second time this month it happened
    >
    > The situation is that both servers are running solaris, A (client) is on
    > 5.10, B (server)is on 5.9.
    >
    > A can mount any other server (windows or Unix) fine, but not B,
    >
    > And B has no problem mounting other file system.
    >
    > umount -f
    > didn't work, it just sit there and doing nothing, I have to do ctrl+c to
    > quit, then I got "bad directory" message.
    >
    > so the only option for me is to reboot to get it fixed.
    >
    > During my diagnose, I found it is interested or maybe I am wrong.
    >
    > disabled May_02 svc:/network/nfs/server:default
    > online May_02 svc:/network/nfs/cbd:default
    > online May_02 svc:/network/nfs/mapid:default
    > online May_02 svc:/network/nfs/status:default
    > online May_02 svc:/network/nfs/nlockmgr:default
    > online May_02 svc:/network/nfs/client:default
    > online May_08 svc:/network/nfs/rquota:default
    >
    >
    >
    > I disable all of them, does that mean that I can't mount any other server
    > because services have been disable?
    >
    > If this is the true, it is funny, because I can still access to other
    > server's exported file system.
    >
    >
    > Please give me some tips
    >
    >


    Try "share" on the server. That should show, IIRC, which file systems
    are being served and which systems are allowed to mount them. It should
    also show HOW the clients are allowed to mount the shared file systems;
    e.g. rw (read-write) or ro (read-only).


  3. Re: Help: NFS mouting issue, Ctrl+C, bad directory

    It looks okay for server side, the trouble is the client just can mount it.

    #share
    - /develop rw=A,root=A ""



    "Richard B. Gilbert" wrote in message
    news:4642270E.9050405@comcast.net...
    > steeles wrote:
    >> Hi all,
    >>
    >> I have to post it again to get further assistance on NFS mapping, as this
    >> is second time this month it happened
    >>
    >> The situation is that both servers are running solaris, A (client) is on
    >> 5.10, B (server)is on 5.9.
    >>
    >> A can mount any other server (windows or Unix) fine, but not B,
    >>
    >> And B has no problem mounting other file system.
    >>
    >> umount -f
    >> didn't work, it just sit there and doing nothing, I have to do ctrl+c to
    >> quit, then I got "bad directory" message.
    >>
    >> so the only option for me is to reboot to get it fixed.
    >>
    >> During my diagnose, I found it is interested or maybe I am wrong.
    >>
    >> disabled May_02 svc:/network/nfs/server:default
    >> online May_02 svc:/network/nfs/cbd:default
    >> online May_02 svc:/network/nfs/mapid:default
    >> online May_02 svc:/network/nfs/status:default
    >> online May_02 svc:/network/nfs/nlockmgr:default
    >> online May_02 svc:/network/nfs/client:default
    >> online May_08 svc:/network/nfs/rquota:default
    >>
    >>
    >>
    >> I disable all of them, does that mean that I can't mount any other server
    >> because services have been disable?
    >>
    >> If this is the true, it is funny, because I can still access to other
    >> server's exported file system.
    >>
    >>
    >> Please give me some tips

    >
    > Try "share" on the server. That should show, IIRC, which file systems are
    > being served and which systems are allowed to mount them. It should also
    > show HOW the clients are allowed to mount the shared file systems; e.g.
    > rw (read-write) or ro (read-only).
    >




+ Reply to Thread