From: Neil Brown <neilb@suse.de>
To: Robin Lee Powell <rlpowell@digitalkingdom.org>
Date: Tue, 21 Aug 2007 09:27:06 +1000
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18122.9034.504690.370294@notabene.brown>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS hang + umount -f: better behaviour requested.
In-Reply-To: message from Robin Lee Powell on Monday August 20
References: <20070820225415.GL3956@digitalkingdom.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1247
Lines: 31

On Monday August 20, rlpowell@digitalkingdom.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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/