From: NeilBrown <neilb@suse.de>
To: Trond Myklebust <trondmy@gmail.com>
Cc: Jeff Layton <jlayton@poochiereds.net>,
Ben Greear <greearb@candelatech.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org
Subject: Re: Killing process in D state on mount to dead NFS server. (when process is in fsync)
Date: Sat, 2 Aug 2014 13:19:46 +1000 [thread overview]
Message-ID: <20140802131946.207c597c@notabene.brown> (raw)
In-Reply-To: <CAABAsM7eh-Faaqmb9yf_xCVwi3cGpnTeOT8A4-e1jhwuEMPKWQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
On Fri, 1 Aug 2014 22:55:42 -0400 Trond Myklebust <trondmy@gmail.com> wrote:
> > That still leaves some open questions though...
> >
> > Is that enough to fix it? You'd still have the dirty pages lingering
> > around, right? Would a umount -f presumably work at that point?
>
> 'umount -f' will kill any outstanding RPC calls that are causing the
> mount to hang, but doesn't do anything to change page states or NFS
> file/lock states.
Should it though?
MNT_FORCE (since Linux 2.1.116)
Force unmount even if busy. This can cause data loss. (Only
for NFS mounts.)
Given that data loss is explicitly permitted, I suspect it should.
Can we make MNT_FORCE on NFS not only abort outstanding RPC calls, but
fail all subsequent RPC calls? That might make it really useful. You
wouldn't even need to "kill -9" then.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-08-02 3:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 18:00 Killing process in D state on mount to dead NFS server Ben Greear
2014-07-31 19:49 ` Malahal Naineni
2014-07-31 19:52 ` Ben Greear
2014-07-31 20:42 ` NeilBrown
2014-07-31 21:20 ` Ben Greear
2014-07-31 21:50 ` Killing process in D state on mount to dead NFS server. (when process is in fsync) NeilBrown
2014-08-01 12:47 ` Jan Kara
2014-08-01 12:47 ` Jan Kara
2014-08-01 12:47 ` Jan Kara
2014-08-02 1:21 ` Jeff Layton
2014-08-02 1:21 ` Jeff Layton
2014-08-02 1:50 ` Roger Heflin
2014-08-02 1:50 ` Roger Heflin
2014-08-02 2:07 ` Jeff Layton
2014-08-02 2:07 ` Jeff Layton
2014-08-02 2:55 ` Trond Myklebust
2014-08-02 2:55 ` Trond Myklebust
2014-08-02 3:19 ` NeilBrown [this message]
2014-08-02 3:44 ` Trond Myklebust
2014-08-02 3:44 ` Trond Myklebust
2014-08-13 15:42 ` Killing process in D state on mount to dead NFS server Ben Greear
2014-08-13 21:18 ` NeilBrown
2014-08-13 21:22 ` Ben Greear
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=20140802131946.207c597c@notabene.brown \
--to=neilb@suse.de \
--cc=akpm@linux-foundation.org \
--cc=greearb@candelatech.com \
--cc=jlayton@poochiereds.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@gmail.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 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.