All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+cert@blue-labs.org>
To: nfs@lists.sourceforge.net
Subject: NFS problems across reboot
Date: Thu, 04 Apr 2002 14:27:56 -0500	[thread overview]
Message-ID: <3CACA93C.5010304@blue-labs.org> (raw)

After rebooting my NFS server, the clients can no longer access the mounts.

A trimmed df shows:

james:/home/james            0         1         0   0% /home/james
james:/home/hnc              0         1         0   0% /home/hnc

# su - xyz
su: warning: cannot change directory to /home/james/x/xyz: Permission denied
bash: /home/james/x/xyz/.bash_profile: Permission denied

However:

# rpcinfo -p james
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100005    1   udp  10000  mountd
    100005    1   tcp  10000  mountd
    100005    2   udp  10000  mountd
    100005    2   tcp  10000  mountd
    100005    3   udp  10000  mountd
    100005    3   tcp  10000  mountd
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100021    1   udp  10001  nlockmgr
    100021    3   udp  10001  nlockmgr
    100021    4   udp  10001  nlockmgr
    100024    1   udp  10002  status
    100024    1   tcp  10001  status

# umount /home/hnc
# mount /home/hnc

And the hnc mount is fine again.  After repeating with /home/james, that 
mount is also fine.

Why do I need to umount and remount?  This is pretty brutal when I need 
to shutdown services so the mounts aren't in use.

These are 2.4.18+ kernels with nfs utils from about a month ago.

David



_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2002-04-04 19:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-04 19:27 David Ford [this message]
2002-04-05  9:12 ` NFS problems across reboot James Pearson
2002-04-07  4:43   ` David Ford
2002-04-07  5:23     ` Neil Brown
2002-04-07  5:44       ` Neil Brown
2002-04-07  6:48         ` David Ford
2002-04-08 13:42         ` James Pearson
2002-04-08 15:23           ` James Pearson
2002-04-08 23:10             ` Neil Brown
2002-04-07  6:39       ` Daniel Freedman
2002-04-08  2:50         ` Neil Brown
2002-04-07  6:59       ` David Ford
2002-04-08  2:48         ` Neil Brown
2002-04-08 12:15           ` Andreas Unterluggauer
2002-04-08 22:58             ` Neil Brown
     [not found] <E16uI1v-00067H-00@usw-sf-list1.sourceforge.net>
2002-04-08  0:43 ` Al Borchers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3CACA93C.5010304@blue-labs.org \
    --to=david+cert@blue-labs.org \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.