Linux NFS development
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Peter Staubach <staubach@redhat.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: umount fails with device busy
Date: Thu, 23 Aug 2007 18:01:47 -0400	[thread overview]
Message-ID: <46CE03CB.4070300@oracle.com> (raw)
In-Reply-To: <46CDF3BE.9030509@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]



Peter Staubach wrote:
> 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.

This is the way Linux implements dirty mmaps on NFS because that's the 
way Linus wants it.  I didn't mean to imply that's the way it *should* 
work, merely the way it *does* work in Linux.

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 315 bytes --]

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

[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-08-23 22:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-23 18:45 umount fails with device busy z00t
2007-08-23 20:03 ` Chuck Lever
2007-08-23 20:14   ` Zoot
2007-08-23 20:32     ` Chuck Lever
2007-08-24 18:52       ` Zoot
2007-08-23 20:29   ` Peter Staubach
2007-08-23 20:35     ` Chuck Lever
2007-08-23 20:53       ` Peter Staubach
2007-08-23 22:01         ` Chuck Lever [this message]
2007-08-24 13:43           ` Peter Staubach
2007-08-23 21:15       ` Zoot
2007-08-23 20:39     ` Zoot
2007-08-23 20:53       ` Peter Staubach
2007-08-23 21:05         ` Zoot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46CE03CB.4070300@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=staubach@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox