From: "Dave Gilbert (Home)" <gilbertd@treblig.org>
To: neilb@cse.unsw.edu.au, nfs@lists.sourceforge.net
Subject: Re: of rmtab and 'Invalid argument' and permission denied]
Date: Thu, 13 Mar 2003 13:43:48 +0000 [thread overview]
Message-ID: <3E708B14.1060000@treblig.org> (raw)
In-Reply-To: 20030309213151.GK747@gallifrey
Neil Brown wrote thus:
that I wrote:
>>Sometimes the client will get a permission denied on attempting to mount
>>from the server even though it managed it a few hours earlier with no
>>change to config of the server.
>>
>>Restarting the nfs server gives a line of the form:
>>
>>clienthostname: Invalid argument
> What does your /etc/exports file look like? Does it have both host
> names and IP addresses?
> Do you export both a directory and an ancestor of that directory on
> the same filesystem?
>
> Both of these can cause this sort of problem.
Thank you! It was exporting both a directory and an ancestor.
Can we have something which screams/shouts/warns/rejects this
rather than failing in an evil and confusing way?
(oh and add it to the NFS FAQ)
> What version of nfs-utils is in SuSE 8.1?
>
> showmount -v
showmount for nfs-utils 0.3.3
Dave
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next parent reply other threads:[~2003-03-13 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030309213151.GK747@gallifrey>
2003-03-13 13:43 ` Dave Gilbert (Home) [this message]
2003-03-14 2:32 ` of rmtab and 'Invalid argument' and permission denied] Neil Brown
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=3E708B14.1060000@treblig.org \
--to=gilbertd@treblig.org \
--cc=neilb@cse.unsw.edu.au \
--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.