Re: umount fails with device busy

[Zoot <z00t@gmx.net>]

On Thu, Aug 23, 2007 at 04:32:50PM -0400, Chuck Lever wrote:
> Zoot wrote:
> >>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.
> >But I had expected that umount blocks until the commit calls are
> > finished as it is with local file systems?
> 
> Sorry, it doesn't.  It has no way of knowing how long those RPCs will take.
> 
> There is a "lazy unmount" facility that removes the NFS share from your 
> client's name space and handles the outstanding RPCs in the background. 
>  I'm not sure if it's working, but you could try "umount -l".
What's with sync() would it wait for the nfs commits? 

-------------------------------------------------------------------------
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