From: Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>
To: NeilBrown <neilb-l3A5Bk7waGM@public.gmane.org>
Cc: Ben Greear <greearb-my8/4N5VtI7c+919tysfdA@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
"linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Killing process in D state on mount to dead NFS server. (when process is in fsync)
Date: Fri, 1 Aug 2014 14:47:34 +0200 [thread overview]
Message-ID: <20140801124734.GB5431@quack.suse.cz> (raw)
In-Reply-To: <20140801075053.2120cb33-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
On Fri 01-08-14 07:50:53, NeilBrown wrote:
> On Thu, 31 Jul 2014 14:20:07 -0700 Ben Greear <greearb-my8/4N5VtI7c+919tysfdA@public.gmane.org> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On 07/31/2014 01:42 PM, NeilBrown wrote:
> > > On Thu, 31 Jul 2014 11:00:35 -0700 Ben Greear <greearb-my8/4N5VtI7c+919tysfdA@public.gmane.org> wrote:
> > >
> > >> So, this has been asked all over the interweb for years and years, but the best answer I can find is to reboot the system or create a fake NFS server
> > >> somewhere with the same IP as the gone-away NFS server.
> > >>
> > >> The problem is:
> > >>
> > >> I have some mounts to an NFS server that no longer exists (crashed/powered down).
> > >>
> > >> I have some processes stuck trying to write to files open on these mounts.
> > >>
> > >> I want to kill the process and unmount.
> > >>
> > >> umount -l will make the mount go a way, sort of. But process is still hung. umount -f complains: umount2: Device or resource busy umount.nfs: /mnt/foo:
> > >> device is busy
> > >>
> > >> kill -9 does not work on process.
> > >
> > > Kill -1 should work (since about 2.6.25 or so).
> >
> > That is -[ONE], right? Assuming so, it did not work for me.
>
> No, it was "-9" .... sorry, I really shouldn't be let out without my proof
> reader.
>
> However the 'stack' is sufficient to see what is going on.
>
> The problem is that it is blocked inside the "VM" well away from NFS and
> there is no way for NFS to say "give up and go home".
>
> I'd suggest that is a bug. I cannot see any justification for fsync to not
> be killable.
> It wouldn't be too hard to create a patch to make it so.
> It would be a little harder to examine all call paths and create a
> convincing case that the patch was safe.
> It might be herculean task to convince others that it was the right thing
> to do.... so let's start with that one.
>
> Hi Linux-mm and fs-devel people. What do people think of making "fsync" and
> variants "KILLABLE" ??
Sounds useful to me and I don't see how it could break some
application...
Honza
--
Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-08-01 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53DA8443.407@candelatech.com>
[not found] ` <20140801064217.01852788@notabene.brown>
[not found] ` <53DAB307.2000206@candelatech.com>
2014-07-31 21:50 ` Killing process in D state on mount to dead NFS server. (when process is in fsync) NeilBrown
[not found] ` <20140801075053.2120cb33-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2014-08-01 12:47 ` Jan Kara [this message]
2014-08-02 1:21 ` Jeff Layton
2014-08-02 1:50 ` Roger Heflin
2014-08-02 2:07 ` Jeff Layton
2014-08-02 2:55 ` Trond Myklebust
2014-08-02 3:19 ` NeilBrown
2014-08-02 3:44 ` Trond Myklebust
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=20140801124734.GB5431@quack.suse.cz \
--to=jack-alswssmvlrq@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=greearb-my8/4N5VtI7c+919tysfdA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=neilb-l3A5Bk7waGM@public.gmane.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;
as well as URLs for NNTP newsgroup(s).