Linux NFS development
 help / color / mirror / Atom feed
From: Greg Banks <gnb@melbourne.sgi.com>
To: Chip Salzenberg <chip@pobox.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: [pme@devphil.com: Bug#239158: Strange exportfs problems, fantastically unhelpful error message]
Date: Mon, 22 Mar 2004 21:12:19 +1100	[thread overview]
Message-ID: <405EBC03.AABE5502@melbourne.sgi.com> (raw)
In-Reply-To: 20040321153515.GW29237@perlsupport.com

Chip Salzenberg wrote:
> 
> This Debian bug report includes an exportfs problem which I suspect is
> due to one export tree under the other, 

Possibly, if one of /usr/local or /home is a symlink to somewhere
underneath the other.

> and an error message complaint
> which I think is justified....

I second this complaint.  On other OSes that case is checked in
userspace early and a sensible message printed, e.g.

irix# exportfs -av
re-exported /
exportfs: /opt: parent-directory (/) already exported
re-exported /mnt/scratch

> I have no idea why the export fails.  If either line is commented, then
> the export succeeds; presumably that's strong evidence of /something/,
> but I don't know the nfs-kernel-server code at all and so can't say what.

You can get a better idea of what is failing by:

linux# echo 4 > /proc/sys/sunrpc/nfsd_debug

linux# exportfs -av
exporting foo.melbourne.sgi.com:/home/fmeh
exporting bar.melbourne.sgi.com:/home/fmeh
exporting foo.melbourne.sgi.com:/home
exporting bar.melbourne.sgi.com:/home
exporting foo.melbourne.sgi.com:/home/fmeh to kernel
exporting bar.melbourne.sgi.com:/home/fmeh to kernel
exporting foo.melbourne.sgi.com:/home to kernel
foo.melbourne.sgi.com:/home: Invalid argument
exporting bar.melbourne.sgi.com:/home to kernel
bar.melbourne.sgi.com:/home: Invalid argument

linux# tail /var/log/messages
...
Mar 22 09:49:53 4A:quux kernel: exp_export called for foo.melbourne.sgi.com:/home
(403/54526548 fl 24).
Mar 22 09:49:53 4A:quux kernel: exp_export: export not valid (Rule 3).  <------
Mar 22 09:49:53 4A:quux kernel: exp_export called for bar.melbourne.sgi.com:/home
(403/54526548 fl 24).
Mar 22 09:49:53 4A:quux kernel: exp_export: export not valid (Rule 3).  <------

The error message tells you...indirectly...what is going on.  You need
to match it to the source of fs/nfsd/export.c:exp_export() to make any
sense of it.  The "Rule 3" message happens when a child of the given
directory is already exported.

Greg.
-- 
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      parent reply	other threads:[~2004-03-22 10:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-21 15:35 [pme@devphil.com: Bug#239158: Strange exportfs problems, fantastically unhelpful error message] Chip Salzenberg
2004-03-22  9:46 ` Olaf Kirch
2004-03-22 10:12 ` Greg Banks [this message]

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=405EBC03.AABE5502@melbourne.sgi.com \
    --to=gnb@melbourne.sgi.com \
    --cc=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