From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Dr. Tilmann Bubeck" <t.bubeck-dx1aEnP5Zukb1SvskN2V4Q@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Is order for "exportfs -r" and rpc.mountd important?
Date: Wed, 3 Dec 2008 12:25:18 -0500 [thread overview]
Message-ID: <20081203172518.GD16846@fieldses.org> (raw)
In-Reply-To: <200811281705.45087.t.bubeck-dx1aEnP5Zukb1SvskN2V4Q@public.gmane.org>
On Fri, Nov 28, 2008 at 05:05:44PM +0100, Dr. Tilmann Bubeck wrote:
> To be more precise: the order between "exportfs -r" and "modprobe nfsd" is
> important (and not "exportfs -r" and "rpc.mountd").
So, I'm confused: what are the before-and-after orders of all three
(modprobe, exportfs, and rpc.mountd)?
>
> Am Freitag, 28. November 2008 15:41:38 schrieb Dr. Tilmann Bubeck:
> > According to manual page "exportfs -r" has two modes: legacy and new.
> > Fedora 10 seems to use the new mode and mounts /proc/fs/nfsd.
> >
> > But they use the following order in /etc/init.d/nfs:
> > exportfs -r
> > rpc.mountd
> >
> > This results in /proc/fs/nfsd/exports having all obsolete entries
> > from /var/lib/nfs/rmtab which causes a lot of trouble with stale NFS file
> > handles.
What problems exactly?
> > This seems to be wrong according to "man exportfs" in new mode.
> >
> > If I change the order to
> > rpc.mountd
> > exportfs -r
> >
> > then everything is OK and /proc/fs/nfsd/exports only contains the info
> > from /etc/exports and not all stale clients. This seems to be correct
> > according to "man exportfs" in new mode.
> >
> > Questions: is this behaviour a bug or at least bad? Shouldn't exportfs
> > being changed, so that when it detects "new" mode it will never feed rmtab
> > into the kernel and rely upon rpc.mountd answering the kernels questions as
> > stated in "man exportfs"?
That does sound wrong.
Perhaps rmtab should also be cleared on exportfs -r? I don't really
understand how rmtab should work.
--b.
> >
> > If yes, then the order or the programs is irrelevant.
> > If not, should the order of the programs be reversed in Fedora?
> >
> > Thanks
> > Till
>
>
>
> --
> +-------+-------------------------------------------------------------+
> | | dr. tilmann bubeck reinform medien- und |
> | | informationstechnologie AG |
> | rein | fon : +49 (711) 7 82 76-52 loeffelstr. 40 |
> | form | fax : +49 (711) 7 82 76-46 70597 stuttgart / germany |
> | AG | cell.: +49 (172) 8 84 29 72 fon: +49 (711) 75 86 56-10 |
> | | email: t.bubeck-dx1aEnP5Zukb1SvskN2V4Q@public.gmane.org http://www.reinform.de |
> | +-------------------------------------------------------------+
> | | pflichtangaben nach paragraph 80, AktG: |
> | | reinform medien- und informationstechnologie AG, stuttgart |
> | | handelsregister stuttgart, HRB 23001 |
> | | vorstand: dr. tilmann bubeck (vorsitz), dr. tommy kuhn |
> | | aufsichtsrat: frank stege (vorsitz) |
> +-------+-------------------------------------------------------------+
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-12-03 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 14:41 Is order for "exportfs -r" and rpc.mountd important? Dr. Tilmann Bubeck
[not found] ` <200811281541.39272.t.bubeck-dx1aEnP5Zukb1SvskN2V4Q@public.gmane.org>
2008-11-28 16:05 ` Dr. Tilmann Bubeck
[not found] ` <200811281705.45087.t.bubeck-dx1aEnP5Zukb1SvskN2V4Q@public.gmane.org>
2008-12-03 17:25 ` J. Bruce Fields [this message]
2008-12-04 9:25 ` Dr. Tilmann Bubeck
[not found] ` <200812041025.02563.t.bubeck-dx1aEnP5Zukb1SvskN2V4Q@public.gmane.org>
2008-12-04 13:59 ` Steve Dickson
[not found] ` <4937E243.1080608-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-12-04 14:16 ` Dr. Tilmann Bubeck
[not found] ` <200812041516.14114.t.bubeck-dx1aEnP5Zukb1SvskN2V4Q@public.gmane.org>
2008-12-04 14:35 ` J. Bruce Fields
2008-12-04 14:43 ` Steve Dickson
2008-12-05 6:05 ` Neil Brown
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=20081203172518.GD16846@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=t.bubeck-dx1aEnP5Zukb1SvskN2V4Q@public.gmane.org \
/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