From: Karsten Hohmeier <karsten@hohmatik.de>
To: NeilBrown <neilb@suse.com>, linux-nfs@vger.kernel.org
Subject: Re: Un-unmountable NFS mountpoints with "Stale NFS file handle" - is this normal behavior?
Date: Thu, 1 Sep 2016 21:07:01 +0200 [thread overview]
Message-ID: <4777cda9-014d-0e58-048e-cfa903fff2da@hohmatik.de> (raw)
In-Reply-To: <87a8fsca7l.fsf@notabene.neil.brown.name>
Thanks for the helpful answer!
> This was fixed 3 years ago in Linux 3.12
I guess it is time to update that machine then ...
>
> Commit: 8033426e6bdb ("vfs: allow umount to handle mountpoints without revalidating them")
>
> (and probably a few other related patches).
>
> You need to be sure you have a version of util-linux where "umount -f"
> and "umount -l" don't stat() the mount point.
>
> NeilBrown
In dev. time terms digging this up is pretty much archeology.
Best regards
Karsten Hohmeier
prev parent reply other threads:[~2016-09-01 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-20 19:03 Un-unmountable NFS mountpoints with "Stale NFS file handle" - is this normal behavior? Karsten Hohmeier
2016-09-01 8:09 ` NeilBrown
2016-09-01 19:07 ` Karsten Hohmeier [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=4777cda9-014d-0e58-048e-cfa903fff2da@hohmatik.de \
--to=karsten@hohmatik.de \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.com \
/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;
as well as URLs for NNTP newsgroup(s).