linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Covici <covici@ccs.covici.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: strange nfs behavior in 2.2.18 and 2.4.0-test12
Date: Thu, 21 Dec 2000 18:16:23 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0012211813110.840-100000@ccs.covici.com> (raw)
In-Reply-To: <14914.32991.480115.210561@notabene.cse.unsw.edu.au>

On Fri, 22 Dec 2000, Neil Brown wrote:

> On Thursday December 21, covici@ccs.covici.com wrote:
> > Hi.  I am having strange nfs problems in both my 2.x and 2.4.0-test12
> > kernels.
> > 
> > What is happening is that when the machine boots up and exports the
> > directories for nfs, it complains that
> > 
> > ccs2:/ invalid argument .
> > 
> > The exports entry is
> > 
> > / ccs2(rw,no_root_squash)
> 
> Is there another export entry that exports another part of the same
> file system to the same client?  If so, that is your problem.

Well I do want to export the mount points under the file system, for
instance I have a partition mounted as /usr and so I have an entry
such as
/usr ccs2(rw,no_root_squash)

in my exports list.  Is there any other way to get this behaviour to
work?

> You cannot export two different directories on the same filesystem to
> the same client if one is an ancestor of the other (because exporting
> a directory is really exporting the directory and all descendants on
> that filesystem, and so exporting a directory and a subdirectory is
> effectively exporting the subdirectory twice with potentially
> different flags).
> 
> NeilBrown
> 
> > 
> > Now in Kernel 2.2.18, if I stop and restart the nfs daemons, all is
> > OK, the invalid argument goes away, but in 2.4.0 I cannot get this to
> > work at all and so I cannot mount nfs from a client on the ccs2 box.
> > I am using the utilities 0.2.1-4 from the Debian distribution if that
> > makes any difference.  I did an strace once on exportfs and it was
> > having trouble with the call to nfsservctl which returns invalid argument.
> > 
> > 
> > Any assistance would be appreciated.
> > 
> > -- 
> >          John Covici
> >          covici@ccs.covici.com
> > 
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > Please read the FAQ at http://www.tux.org/lkml/
> 

-- 
         John Covici
         covici@ccs.covici.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-21 23:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-21 18:37 strange nfs behavior in 2.2.18 and 2.4.0-test12 John Covici
2000-12-21 19:01 ` Charles Wilkins
2000-12-21 22:14 ` Neil Brown
2000-12-21 23:16   ` John Covici [this message]
2000-12-21 23:21     ` Neil Brown
2000-12-21 23:35       ` John Covici
2000-12-22  0:15         ` Andreas Dilger
2000-12-22  0:42           ` John Covici

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=Pine.LNX.4.21.0012211813110.840-100000@ccs.covici.com \
    --to=covici@ccs.covici.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).