From: Chip Salzenberg <chip@pobox.com>
To: nfs@lists.sourceforge.net
Subject: Bug#148482: 'nfs-kernel-server reload' immediately stales all nfs handles
Date: Sun, 15 Sep 2002 18:19:31 -0400 [thread overview]
Message-ID: <20020915221931.GE11002@perlsupport.com> (raw)
So is 'exportfs -r' *supposed* to stale all NFS handles? If so, is this
adequately documented? adTHANKSvance
----- Forwarded message from Herbert Xu <herbert@gondor.apana.org.au> -----
Package: kernel
Version: N/A; reported 2002-05-29
Severity: grave
Justification: causes non-serious data loss
While diagnosing an autofs problem with a particular client, I wanted to reload
changes to the /etc/exports file into the kernel nfs server. I ran:
/etc/init.d/nfs-kernel-server reload
which basically runs the command:
exportfs -r
The man page for this command does not indicate this is a destructive action
and I know I have run this same command on previous versions of the kernel with
no problems.
The result this time was that every client with automounted home directories
immediately got stale file handles which caused them to lose access to their
running apps. We had to go to each client to manually restart autofs on each
client to restore the nfs file handles. Unfortunately, many people lost the
files they were working on.
----- End forwarded message -----
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
"It furthers one to have somewhere to go."
-------------------------------------------------------
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 reply other threads:[~2002-09-15 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-15 22:19 Chip Salzenberg [this message]
2002-09-15 23:02 ` Bug#148482: 'nfs-kernel-server reload' immediately stales all nfs handles 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=20020915221931.GE11002@perlsupport.com \
--to=chip@pobox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox