From: NeilBrown <neilb@suse.de>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: wow
Date: Tue, 23 Aug 2011 10:24:44 +1000 [thread overview]
Message-ID: <20110823102444.2bc6d1c7@notabene.brown> (raw)
In-Reply-To: <CCE4A253-3046-45EA-92E2-1C384AC64917@oracle.com>
On Mon, 22 Aug 2011 15:15:06 -0400 Chuck Lever <chuck.lever@oracle.com> wrote:
> http://www.linuxjournal.com/content/how-release-stuck-nfs-mounts-without-reboot
>
That brings back memories... I've definitely had a case where I added a
an extra IP address to some server so it could pretend to be a dead serve and
allow the mount points to fail and processes to be killed.
With lazy unmounts and TASK_KILLABLE that should all be a think of the past
though ... I hope.
NeilBrown
prev parent reply other threads:[~2011-08-23 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 19:15 wow Chuck Lever
2011-08-23 0:24 ` NeilBrown [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=20110823102444.2bc6d1c7@notabene.brown \
--to=neilb@suse.de \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox