From: Karel Zak <kzak@redhat.com>
To: Phillip Susi <psusi@ubuntu.com>
Cc: util-linux@vger.kernel.org
Subject: Re: Can't unmount broken nfs mount
Date: Mon, 17 Feb 2014 13:19:43 +0100 [thread overview]
Message-ID: <20140217121943.GE2254@x2.net.home> (raw)
In-Reply-To: <52F95FD1.5090305@ubuntu.com>
On Mon, Feb 10, 2014 at 06:25:05PM -0500, Phillip Susi wrote:
> Forwarding from debian bug #711183:
>
> User reports that a broken nfs mount has its mounted directory in
> /proc/mounts renamed from /foo to /foo\040(deleted) when an nfs mount
> is broken due to an unreachable server, and this prevents unmounting
> it since umount can not find "/foo" in /proc/mounts. Is this a kernel
> bug, or something that umount needs to work around?
I have improved the mountinfo libmount parser, now it removes the
"\040(deleted)" from the target path. You can try it with NFS.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2014-02-17 12:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 23:25 Can't unmount broken nfs mount Phillip Susi
2014-02-11 9:30 ` Karel Zak
2014-02-17 12:19 ` Karel Zak [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=20140217121943.GE2254@x2.net.home \
--to=kzak@redhat.com \
--cc=psusi@ubuntu.com \
--cc=util-linux@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