From: Martin Pool <mbp@sourcefrog.net>
To: Bernd Schubert <bernd-schubert@web.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: no_subtree_check questions
Date: Fri, 29 Aug 2003 15:13:40 +1000 [thread overview]
Message-ID: <20030829151340.150a0ae5.mbp@sourcefrog.net> (raw)
In-Reply-To: <200308290206.49232.bernd-schubert@web.de>
On 29 Aug 2003 Bernd Schubert <bernd-schubert@web.de> wrote:
> Hello,
>
> as I understand it, the sub_tree_check is only neccessary if the
> filesystem is not exported at its root. Wouldn't it make sense to let
> the nfs-utils automatically recognise that and then automatically set
> the option no_subtree_check? I mean this could be implemented
> easily...
Of course that would just make the behaviour incosistent and hard to
debug. (I might not have been able to work out what was wrong in the
original bug report, for example.) I'm not really a fan of fixes that
just fix some circumstances.
> Also, I would like to know what happens if one sets the
> no_subtree_check-option and re-exports the /etc/exportfs on the server
> or restarts the nfsd, but the clients still have mounted the
> directory? I'm a bit scared since the man-page says that the
> filehandle is modified for this check.
I think the clients need to remount the filesystem, because all the
filehandles become invalid. Even the root of the filesystem can't be
found. Perhaps I just did something wrong though.
--
Martin
-------------------------------------------------------
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-29 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 1:03 nfs/mmap/rename file corruption Martin Pool
2003-08-28 1:37 ` Trond Myklebust
2003-08-28 2:14 ` Martin Pool
2003-08-28 14:04 ` Trond Myklebust
2003-08-29 0:06 ` no_subtree_check questions Bernd Schubert
2003-08-29 5:13 ` Martin Pool [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=20030829151340.150a0ae5.mbp@sourcefrog.net \
--to=mbp@sourcefrog.net \
--cc=bernd-schubert@web.de \
--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.