From: Tom McNeal <trmcneal@attbi.com>
To: Kapeller Rene PSI <rene.kapeller@psi.ch>
Cc: Stuart Sheldon <stu@actusa.net>, nfs@lists.sourceforge.net
Subject: Re: take away nfs write permissions instantly
Date: Thu, 20 Jun 2002 09:44:39 -0700 [thread overview]
Message-ID: <3D120677.4FDBE4E3@attbi.com> (raw)
In-Reply-To: 3D11ED7D.50407@psi.ch
Hi -
Since the mount has taken place, I wouldn't expect that
modifying the export would change things, unless you
also modified the file system on the server in order to
prevent write accesses from taking place at all. Even then,
it wouldn't necessarily take place instantly due to caches
on the client, in PV2. It would probably be much faster
in PV3, since you'd see the attribute change after the
next transaction, but it still wouldn't be instantaneous.
I don't know if there is a way to do what you want to do.
(This is my instant reaction, so take it with the standard
grain of salt...)
Tom
Kapeller Rene PSI wrote:
>
> exportfs -r did not help either!
> (Since I do not fully understand the difference between exportfs -a and
> exportfs -r, I usually do both.)
>
> Btw, I'm using RedHat-7.3 (nfs-utils-0.3.3) on the Linux side.
>
> Rene
>
> Stuart Sheldon wrote:
> > Did you run exportfs -r after you changed exports?
> >
> > Stu
> >
> >
> > Kapeller Rene PSI wrote:
> >
> >> Can anyone help me on the following problem:
> >>
> >> In order to take away nfs write permissions instantly for a previously
> >> mounted
> >> nfs directory called '/data', I'm changing the export options for '/data'
> >> on the server to 'ro', while keeping the mount on the client.
> >>
> >> exportfs -io ro,sync,wdelay,no_root_squash nfsclient:/data
> >>
> >> exportfs -v
> >> /data nfsserver(ro,wdelay,no_root_squash)
> >>
> >> Surprisingly the client can still write to /data at this point, unless
> >> I do
> >> umount/mount of /data.
> >>
> >> Is this the way it's suposed to work?
> >>
> >> Changing the nfs export options on a SunOS 5.6 while clients have
> >> mounted
> >> a nfs path, write permissions are instantly taken away from it.
> >>
> >> share -F nfs -o ro,root=nfsclient /data
> >>
> >> In both cases I used the following nfs mount options:
> >> mount -o rw,sync,nfsvers=3,wsize=32768,rsize=32768
> >>
> >> Thanks!
> >> - Rene
--
------------------------------------------------------------
Tom McNeal trmcneal@attbi.com (650)906-0761 (cell)
------------------------------------------------------------
-------------------------------------------------------
Bringing you mounds of caffeinated joy
>>> http://thinkgeek.com/sf <<<
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-06-20 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 10:39 take away nfs write permissions instantly Kapeller Rene PSI
2002-06-20 14:24 ` Stuart Sheldon
2002-06-20 14:58 ` Kapeller Rene PSI
2002-06-20 16:44 ` Tom McNeal [this message]
2002-06-21 3:00 ` Neil Brown
2002-06-21 3:47 ` Kapeller Rene PSI
2002-06-21 5:13 ` Neil Brown
2002-06-21 14:57 ` Bernd Schubert
2002-06-21 18:04 ` Tom McNeal
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=3D120677.4FDBE4E3@attbi.com \
--to=trmcneal@attbi.com \
--cc=nfs@lists.sourceforge.net \
--cc=rene.kapeller@psi.ch \
--cc=stu@actusa.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.