From: Marc Schmitt <mschmitt@inf.ethz.ch>
Cc: nfs@lists.sourceforge.net
Subject: Re: Large export list leads to "Invalid argument" errors when executing 'exportfs -r'
Date: Thu, 28 Aug 2003 10:56:14 +0200 [thread overview]
Message-ID: <3F4DC3AE.7040003@inf.ethz.ch> (raw)
In-Reply-To: <1057405449.3361.64.camel@localhost>
Marc Schmitt wrote:
>Hi all,
>
>I'm using RedHat 7.3 as NFS server, kernel 2.4.18-27.7.xsmp, nfs-utils
>1.0.3.
>
>For each home directory, we make an entry into /etc/exports of the type:
>
>/export/home/<login> @<login>(rw,sync)
>
>The @<login> netgroups contain usually a whole bunch of machines in FQDN
>notation.
>
>This setup used to work fine, I could add a new entry to /etc/exports
>and issue 'exportfs -r' and everything would work as expected, the new
>home could be mounted on the machines in @<login>.
>
>Somehow, with /etc/exports growing more and more (currently 137
>entries), 'exportfs -r' started giving errors of the type:
>
><somehost part of @<login>>:/export/home/<login>: Invalid argument
>
>Currently, I get three of those error lines for three entries in
>/etc/exports. Lokks like it fails when it tries to unexport the entry,
>'exportsfs -r -v' shows:
>
>unexporting <somehost part of @<login>>:/export/home/<login> from kernel
><somehost part of @<login>>:/export/home/<login>: Invalid argument
>
>I made several tests, even when I delete the line in /etc/exports for
><login>, 'exportfs -r' will still give this error. I've deleted the
>corresponding entry in /var/lib/nfs/xtab but 'exportfs -r' would just
>add it again, obviously it's cached in the kernel table.
>
>Looking at 'showmount -a', I noticed that the server thinks, that
><somehost> has /export/home/<login> mounted, still. Even though the
>client does not have the home mounted from the server. I mounted the
>home on <somehost>, unmounted and issued 'exportfs -r' on the server and
>the error message "somehost part of @<login>>:/export/home/<login>:
>Invalid argument" did not appear again.
>
FYI: this problem went away with the update from nfs-utils 1.0.3 to
1.0.5. Since the update, even though the export table has grown
considerably again menawhile, I have not seen the "Invalid argument"
error again.
Greetz
Marc
-------------------------------------------------------
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
prev parent reply other threads:[~2003-08-28 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 11:44 Large export list leads to "Invalid argument" errors when executing 'exportfs -r' Marc Schmitt
2003-07-07 10:14 ` Marc Schmitt
2003-08-28 8:56 ` Marc Schmitt [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=3F4DC3AE.7040003@inf.ethz.ch \
--to=mschmitt@inf.ethz.ch \
--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