Linux NFS development
 help / color / mirror / Atom feed
From: Chip Salzenberg <chip@pobox.com>
To: nfs@lists.sourceforge.net
Subject: User report: Asymmetric mount failures
Date: Sun, 15 Sep 2002 18:03:21 -0400	[thread overview]
Message-ID: <20020915220321.GC11002@perlsupport.com> (raw)

I would appreciate some help diagnosing this Debian NFS bug report.
If they're using up-to-date Debian unstable as they say, they'll have
been using nfs-utils 1.0 on both machines.

----- Forwarded message from Nick Bailey <n.j.bailey@elec.gla.ac.uk> -----

Subject: Bug#81428: Possibly related mound problem?
From: Nick Bailey <n.j.bailey@elec.gla.ac.uk>
To: 81428@bugs.debian.org
Date: Tue, 06 Aug 2002 18:34:24 +0100

Hi!

I've been having serious difficulty using NFS-kernel-server too, and now 
have the situation where with identical hosts.{deny,allow} and exports, 
machine A can mount /etc from machine B, but not the other way around 
(I'm just using /etc for testing, of course)

So,

root@strauss:/etc# mount -t nfs cmtdb121:/etc /tmp/qqq

On cmtdb121, syslog shows:
Aug  6 18:26:54 cmtdb121 rpc.mountd: authenticated mount request from 
strauss:955 for /etc (/etc)

but...

cmtdb121:/etc# mount -t nfs strauss:/etc /tmp/qqq
mount: strauss:/etc failed, reason given by server: Permission denied

and strauss shows in its syslog:

Aug  6 18:27:25 strauss rpc.mountd: refused mount request from cmtdb121 
for /etc (/): no export entry

I note /etc is somehow referred to / on strauss (no idea why, but this 
would seem to be the cause of the problem), whereas it's correctly 
resolved as /etc on cmtdb121

cmtdb121 is a powerpc, Linux cmtdb121 2.4.18-powerpc #1 Thu Mar 14 
16:55:14 EST 2002 ppc unknown unknown GNU/Linux
Strauss is a dual AMD box with 2 NICs (one unconfigured): Linux strauss 
2.4.18-686-smp #2 SMP Wed Mar 20 20:24:14 EST 2002 i686 unknown unknown 
GNU/Linux

Both of bang-up-to-date Sid installs. the portmapper, nfs-common and 
nfs-kernel-servers have all been stopped and started in the appropriate 
order several times.

Two sysadmins and I have spent almost a whole day on this: I don't think 
it's obvious (although I'm pretty thick at reporting bugs sometimes and 
have dropped a few bricks, at least the sysadmins agree with me this time :)

If there are any other test I could make, please don't hesitate to ask.

Nick/

-- 
Dr Nick Bailey                              n.j.bailey@elec.gla.ac.uk
Centre for Music Technology                 http://cmt.gla.ac.uk/
Dept of Electronics and Electrical Eng      http://www.elec.gla.ac.uk/
The University of Glasgow                   http://www.gla.ac.uk

----- End forwarded message -----

-- 
Chip Salzenberg         - a.k.a.  -        <chip@pobox.com>
         "It furthers one to have somewhere to go."


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2002-09-15 22:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020915220321.GC11002@perlsupport.com \
    --to=chip@pobox.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox