Skip to contentSkip to conversation

Can't unmount broken nfs mount

DISCUSSION Phillip Susi 2 participants 3 messages Feb 10, 2014 – Feb 17, 2014 Util-Linux package

lore
Share & tools
lore

Phillip Susi

author
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

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?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJS+V/RAAoJEI5FoCIzSKrwrSYIAIabY0n6tptzm+DenwAv8cf4 fb7bb7+rcjXXpeYEzyD7xIDvmRgNuYoxMOdTfRkMeR04K4E8MDKx98pH0WU8m2CY SQh0WCVKStxNFYOd8DugeRYP0kaisyhoe43XtKyHGjwvpNXIjDEsPFV30Rw1cLQa OJD2FrZLNUhciuvzRXl17mmUowWqGa9QqoVA54Hn2dkgmP3Arlkx+11cxwxD3zE1 OXplSvugMfwgDugLawdorDrUl37Efv47+l4yW6ZiLjhb6cu8QxDQDpaTgHLXtFJi ZBECGDbKDDEBbNWGvjSkY40CaTiZeEXn5DePYQkY1iaq8TfhXHi/YTg21w7Srgg= =dvV4
-----END PGP SIGNATURE-----

maintainer
#1 lore raw
Quoted 10 lines · Phillip Susi

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

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 don't think this is a kernel bug, we already support "(deleted)" for /proc/swaps in libmount. All we need is to improve libmount/src/tab_parse.c to supports this suffix in mount tables too.

Karel

Signature · 2 lines
 Karel Zak  <[email protected]>
 http://karelzak.blogspot.com
maintainer
#2 lore raw
In reply to Phillip Susi
Quoted 7 lines · Phillip Susi

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

Signature · 2 lines
 Karel Zak  <[email protected]>
 http://karelzak.blogspot.com