All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chip Salzenberg <chip@pobox.com>
To: nfs@lists.sourceforge.net
Subject: [pme@devphil.com: Bug#239158: Strange exportfs problems, fantastically unhelpful error message]
Date: Sun, 21 Mar 2004 10:35:15 -0500	[thread overview]
Message-ID: <20040321153515.GW29237@perlsupport.com> (raw)

This Debian bug report includes an exportfs problem which I suspect is
due to one export tree under the other, and an error message complaint
which I think is justified....

----- Forwarded message from Phil Edwards <pme@devphil.com> -----

Subject: Bug#239158: Strange exportfs problems, fantastically unhelpful error message
From: Phil Edwards <pme@devphil.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Date: Sun, 21 Mar 2004 00:37:43 -0500

Package: nfs-kernel-server
Version: 1:1.0.6-1
Severity: normal

    [~]# cat /etc/exports
    /usr/local      fenric(ro,async) hreidmar(ro,async)
    /home           fenric(rw,sync) hreidmar(rw,sync)
    [~]# exportfs -v -r
    exporting hreidmar:/usr/local
    exporting fenric:/usr/local
    exporting hreidmar:/home
    exporting fenric:/home
    exporting hreidmar:/usr/local to kernel
    hreidmar:/usr/local: Invalid argument
    exporting fenric:/usr/local to kernel
    fenric:/usr/local: Invalid argument
    reexporting hreidmar:/home to kernel
    reexporting fenric:/home to kernel
    [~]#

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.

My real complaint is that "Invalid argument" doesn't tell me a damn thing,
so I have no idea what to try next.


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux fenric 2.4.22-fenric3 #1 SMP Sun Oct 12 00:45:53 EDT 2003 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages nfs-kernel-server depends on:
ii  debconf                     1.4.7        Debian configuration management sy
ii  libc6                       2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  libwrap0                    7.6-ipv6.1-3 Wietse Venema's TCP wrappers libra
ii  nfs-common                  1:1.0.6-1    NFS support files common to client
ii  sysvinit                    2.85-9       System-V like init.

-- debconf information:
  nfs-kernel-server/sync-default: 
  nfs-kernel-server/tcpwrappers-mountd: 




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

-- 
Chip Salzenberg               - a.k.a. -               <chip@pobox.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
    but he stepped in a wormhole and had to go in early."  // MST3K


-------------------------------------------------------
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

             reply	other threads:[~2004-03-21 15:35 UTC|newest]

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

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=20040321153515.GW29237@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 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.