All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Pearson <james-p@moving-picture.com>
To: Jeremy Sanders <jss@ast.cam.ac.uk>
Cc: nfs@lists.sourceforge.net
Subject: Re: Permission denied
Date: Wed, 07 May 2003 17:21:25 +0100	[thread overview]
Message-ID: <3EB93285.F40CC32A@moving-picture.com> (raw)
In-Reply-To: Pine.LNX.4.55.0305071639490.2587@xpc5.ast.cam.ac.uk

What version of nfs-utils are you running on the server?

I had a problem if the server crashed before a client mount could be
recorded to /var/lib/nfs/rmtab, the client got permission denied on the
mount point after the server rebooted - see:

http://marc.theaimsgroup.com/?l=linux-nfs&m=101828003630443&w=2

This is fixed in the more recent versions of nfs-utils.

Also, if you manually attempt to umount an NFS file system (automounted
or not), but the umount fails because the file system is busy - this
will cause a problem as rpc.mountd on the server has already removed the
client from /var/lib/nfs/rmtab - which means if the server reboots, the
server has no record of the client mount, so you get permission denied
on client when it accesses the mount point ... see:

http://marc.theaimsgroup.com/?l=linux-nfs&m=104558814532107&w=2

I had this problem - my work round is not to manually umount automounted
file systems ... (or, if I have to, use a hacked version of umount that
doesn't contact rpc.mountd on the server).

James Pearson

Jeremy Sanders wrote:
> 
> I've seen this problem a couple of times (I think I reported it to the
> list before but I can find the posting). Using the automounter to mount
> home directories (rw,v3,rsize=8192,wsize=8192,hard,intr,udp,lock), it
> seems that rebooting a Linux server can give a "Permission denied" on
> the client. Further attempts at accessing the mountpoint give this error.
> It can be fixed my umounting it (if nothing is using it), and reaccessing
> the mountpoint.
> 
> The server is running RedHat's 2.4.18-27.7.x kernel, and the client is
> using 2.4.18-17.7.x (unfortunately).
> 
> dmesg on the client shows:
> 
> nfs: server server.ast.cam.ac.uk not responding, still trying
> nfs: task 57889 can't get a request slot
> nfs: server server.ast.cam.ac.uk OK
> nfs: server server.ast.cam.ac.uk OK
> 
> sendmail gave errors such as:
> 
> May  7 16:07:39 xserv1 sendmail[22255]: h47EwYl22254: forward
> /home/gmorris: transient error: Timeout on file open
> May  7 16:07:39 xserv1 sendmail[22195]: h47Eljl22194: forward
> /home/gmorris: transient error: Timeout on file open
> May  7 16:07:39 xserv1 sendmail[22255]: h47EwYl22254: forward
> /home/gmorris/.forward: Permission denied
> May  7 16:07:39 xserv1 sendmail[22195]: h47Eljl22194: forward
> /home/gmorris/.forward: Permission denied
> 
> Any ideas? I suppose it's hard to diagnose this without a network traffic
> analysis, and we're not using the standard kernel either. I suppose it
> could be an automounter bug.
> 
> Jeremy
> 
> --
> Jeremy Sanders <jss@ast.cam.ac.uk>   http://www-xray.ast.cam.ac.uk/~jss/
> X-Ray Group, Institute of Astronomy, University of Cambridge, UK.
> Public Key Server PGP Key ID: E1AAE053
> 
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
> 
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

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

  reply	other threads:[~2003-05-07 16:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 15:47 Permission denied Jeremy Sanders
2003-05-07 16:21 ` James Pearson [this message]
2003-05-07 16:32   ` Jeremy Sanders
2003-05-07 16:31 ` Trond Myklebust
2003-05-07 16:34   ` Jeremy Sanders
  -- strict thread matches above, loose matches on Subject: below --
2006-02-07 11:34 Daniel Bramkamp
2006-02-07 11:52 ` Tradebit Service
2006-02-07 13:04   ` Daniel Bramkamp
     [not found] ` <20060220112535.GA10567@janus>
2006-02-20 12:16   ` Daniel Bramkamp
2006-02-20 14:31     ` Trond Myklebust
2006-02-20 15:43       ` Daniel Bramkamp
2002-11-21 20:42 permission denied Rongqing "Frank" Tu
2002-11-21 23:34 ` Neil Brown
2002-11-22 16:11   ` Rongqing "Frank" Tu
2002-11-23 18:22     ` Bernd Schubert
2002-11-24  3:03       ` Rongqing "Frank" Tu

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=3EB93285.F40CC32A@moving-picture.com \
    --to=james-p@moving-picture.com \
    --cc=jss@ast.cam.ac.uk \
    --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.