Linux NFS development
 help / color / mirror / Atom feed
From: Zoot <z00t@gmx.net>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: umount fails with device busy
Date: Thu, 23 Aug 2007 23:15:20 +0200	[thread overview]
Message-ID: <20070823211520.GC4822@localhost> (raw)
In-Reply-To: <46CDEF90.90007@oracle.com>

On Thu, Aug 23, 2007 at 04:35:28PM -0400, 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.
At least according to the NFS debug output are the commits only related
to .trc files which are used by the app to store it's debug output. Not
used for mmap.

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

  parent reply	other threads:[~2007-08-23 21:15 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
2007-08-24 13:43           ` Peter Staubach
2007-08-23 21:15       ` Zoot [this message]
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=20070823211520.GC4822@localhost \
    --to=z00t@gmx.net \
    --cc=chuck.lever@oracle.com \
    --cc=nfs@lists.sourceforge.net \
    /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