From: Bernd Schubert <bernd-schubert@web.de>
To: trond.myklebust@fys.uio.no, Martin Pool <mbp@sourcefrog.net>
Cc: nfs@lists.sourceforge.net
Subject: no_subtree_check questions
Date: Fri, 29 Aug 2003 02:06:48 +0200 [thread overview]
Message-ID: <200308290206.49232.bernd-schubert@web.de> (raw)
In-Reply-To: <16206.3062.480403.590086@charged.uio.no>
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...
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.
Though we never had problems like Martin (at least we didn't notice), I don't
think this check makes sense in our environment.
Thanks,
Bernd
-------------------------------------------------------
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
next prev parent reply other threads:[~2003-08-29 0:10 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 ` Bernd Schubert [this message]
2003-08-29 5:13 ` no_subtree_check questions Martin Pool
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=200308290206.49232.bernd-schubert@web.de \
--to=bernd-schubert@web.de \
--cc=mbp@sourcefrog.net \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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