From: "J. Bruce Fields" <bfields@fieldses.org>
To: devzero@web.de
Cc: linux-nfs@vger.kernel.org, pf@artcom-gmbh.de, rnews@altium.nl,
jlayton@redhat.com
Subject: Re: How to avoid rebooting Linux NFS-client when NFS-server is not available?
Date: Thu, 8 Jun 2017 09:34:23 -0400 [thread overview]
Message-ID: <20170608133423.GG26995@fieldses.org> (raw)
In-Reply-To: <trinity-f2c19596-3afe-4a3f-ad07-78e6cfda9cb5-1496911790012@3capp-webde-bap34>
On Thu, Jun 08, 2017 at 10:49:50AM +0200, devzero@web.de wrote:
> Any hint on how to circumvent rebooting to remount the nfs share or proactively avoid stale NFS mounts would be very appreciated. (disabling NFS by module unload/load is no option, as our XEN servers do have other NFS mounts for shared storage)
Neil had some recent posts that might be relevant:
http://marc.info/?l=util-linux-ng&m=149662998931157&w=2
Ripping out the storage from underneath your applications is a pretty
drastic step and may lose data, so NFS hasn't traditionally tried very
hard to make it easy. But it may be possible at this point if you kill
-9 all the users and umount carefully.
> I`m not sure if linux-nfs ML will allow anonymous posts (probably
> not), so maybe someone subscribed be so kind to reply with list cc´ed.
> I`d like to avoid subscribing to a list because of a single post...
That's fine.
--b.
next prev parent reply other threads:[~2017-06-08 13:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 8:49 How to avoid rebooting Linux NFS-client when NFS-server is not available? devzero
2017-06-08 13:34 ` J. Bruce Fields [this message]
2017-06-08 14:06 ` Aw: " devzero
2017-06-08 14:55 ` J. Bruce Fields
2017-06-09 3:17 ` NeilBrown
-- strict thread matches above, loose matches on Subject: below --
2013-07-24 9:18 Peter Funk
2013-07-24 11:24 ` Jeff Layton
2013-07-24 13:03 ` Dick Streefland, rnews
2013-07-26 12:08 ` Peter Funk
2013-07-26 14:31 ` Michael Richardson
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=20170608133423.GG26995@fieldses.org \
--to=bfields@fieldses.org \
--cc=devzero@web.de \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=pf@artcom-gmbh.de \
--cc=rnews@altium.nl \
/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.