From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: David Fries <dfries@umr.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stale NFS handles on 2.4.2
Date: 25 Feb 2001 15:00:11 +0100 [thread overview]
Message-ID: <shsvgpyual0.fsf@charged.uio.no> (raw)
In-Reply-To: <20010214002750.B11906@unthought.net> <20010224141855.B12988@d-131-151-189-65.dynamic.umr.edu>
In-Reply-To: David Fries's message of "Sat, 24 Feb 2001 14:18:55 -0600"
>>>>> " " == David Fries <dfries@umr.edu> writes:
> I'ved tried `mount /home -o remount`, and reading lots of other
> directories to flush out that entry if it was in cache without
> any results.
> I was hopping to avoid unmounting, as I would have to shut
> about everything down to do that.
It looks as if you'll have to do that. 'mount -oremount' does not
really cause the root filehandle to get updated. The only thing it
does at the moment is allow you to change from a read-only to a
read-write filesystem.
What kind of filesystem is this BTW: is it an ext2 partition you are
exporting?
Cheers,
Trond
next prev parent reply other threads:[~2001-02-25 14:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 23:27 Stale NFS handles on 2.4.1 Jakob Østergaard
2001-02-13 23:31 ` Alan Cox
2001-02-13 23:43 ` Jakob Østergaard
2001-02-14 8:35 ` Rogier Wolff
2001-02-14 0:02 ` Trond Myklebust
2001-02-24 20:18 ` Stale NFS handles on 2.4.2 David Fries
2001-02-25 5:43 ` Neil Brown
2001-02-25 5:53 ` David Fries
2001-02-25 9:25 ` Neil Brown
2001-02-25 19:10 ` David Fries
2001-02-28 0:12 ` Neil Brown
2001-02-28 12:02 ` Trond Myklebust
2001-02-28 22:15 ` Neil Brown
2001-03-01 1:13 ` Trond Myklebust
[not found] ` <20010228211808.C24668@d-131-151-189-65.dynamic.umr.edu>
2001-03-01 9:07 ` Trond Myklebust
[not found] ` <s5gwva9simp.fsf@egghead.curl.com>
2001-03-01 14:13 ` Stale NFS handles on 2.4.2^H^H^H^H^H2.2.19 Trond Myklebust
2001-02-25 14:00 ` Trond Myklebust [this message]
2001-02-26 9:54 ` Stale NFS handles on 2.4.2 Lennert Buytenhek
2001-02-26 15:56 ` David Fries
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=shsvgpyual0.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=dfries@umr.edu \
--cc=linux-kernel@vger.kernel.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 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.