linux-kernel - Re: NFS hang + umount -f: better behaviour requested.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <18122.9034.504690.370294@notabene.brown>
Date:	Tue, 21 Aug 2007 09:27:06 +1000
From:	Neil Brown <neilb@...e.de>
To:	Robin Lee Powell <rlpowell@...italkingdom.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: NFS hang + umount -f: better behaviour requested.

On Monday August 20, rlpowell@...italkingdom.org wrote:
> (cc's to me appreciated)
> 
> It would be really, really nice if "umount -f" against a hung NFS
> mount actually worked on Linux.  As much as I hate Solaris, I
> consider it the gold standard in this case: If I say
> "umount -f /mount/that/is/hung" it just goes away, immediately, and
> anything still trying to use it dies (with EIO, I'm told).

Have you tried "umount -l"?   How far is that from your requirements?

Alternately:
   mount --move /problem/path /somewhere/else
   umount -f /somewhere/else
   umount -l /somewhere/else

might be a little closer to what you want.

Though I agree that it would be nice if we could convince all
subsequent requests to a server to fail EIO instead of just the
currently active ones.  I'm not sure that just changing "umount -f" is
the right interface though....  Maybe if all the server handles
appeared in sysfs and have an attribute which you could set to cause
all requests to fail...

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/