Re: umount fails with device busy

[Peter Staubach <staubach@redhat.com>]

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