From: Peter Staubach Subject: Re: umount fails with device busy Date: Thu, 23 Aug 2007 16:53:18 -0400 Message-ID: <46CDF3BE.9030509@redhat.com> References: <20070823184544.237460@gmx.net> <46CDE805.4090909@oracle.com> <46CDEE3A.3040809@redhat.com> <46CDEF90.90007@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: nfs@lists.sourceforge.net To: chuck.lever@oracle.com Return-path: Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91] helo=mail.sourceforge.net) by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43) id 1IOJg7-0005B8-4Z for nfs@lists.sourceforge.net; Thu, 23 Aug 2007 13:53:19 -0700 Received: from mx1.redhat.com ([66.187.233.31]) by mail.sourceforge.net with esmtp (Exim 4.44) id 1IOJgA-0006nL-AV for nfs@lists.sourceforge.net; Thu, 23 Aug 2007 13:53:23 -0700 In-Reply-To: <46CDEF90.90007@oracle.com> List-Id: "Discussion of NFS under Linux development, interoperability, and testing." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfs-bounces@lists.sourceforge.net Errors-To: nfs-bounces@lists.sourceforge.net Chuck Lever wrote: >>>> When I run umount during these ops I get an device busy. Any help >>>> would be very appreciated! >>> >>> This is normal and expected behavior. One problem may be that your >>> server is slow, and thus there are RPCs left outstanding for a bit >>> on your client after your application exits. The COMMIT calls from >>> that trace suggest that there is dirty data the client is writing >>> back to the server. >> >> It seems to me that this should not be the expected behavior unless >> the file system is mounted "nocto". Is it? > > I'm a little puzzled myself about what dirty data there might be left > after the application quits. However, I'll be there is an mmap() > lurking somewhere in the background... > > Data that was dirtied via a mapped file is not subject to the > writeback part of close-to-open. I don't think that I agree with this last statement. Although it can not be implemented using the normal close system call, something should trigger the flush of any dirty pages and wait for them to complete. I view close-to-open as a semantic and not just as a syntax. I view it as "check on first reference" and "flush when last reference is released". Thanx... ps ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs