CEPH filesystem development
 help / color / mirror / Atom feed
From: Thomas Mueller <thomas@chaschperli.ch>
To: ceph-devel@vger.kernel.org
Subject: Re: "VFS: Busy inodes after unmount of ceph" kernel-message after umount
Date: Tue, 8 Jun 2010 08:34:50 +0000 (UTC)	[thread overview]
Message-ID: <hukvba$f6o$1@dough.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.1006072209280.3013@cobra.newdream.net

Am Mon, 07 Jun 2010 22:21:33 -0700 schrieb Sage Weil:

>> > On Sat, 5 Jun 2010, Thomas Mueller wrote:
>> >> hi
>> >> 
>> >> since running an new snapshot test* that creates some(many?)
>> >> snapshots I get this kernel message on umount:
>> >> 
>> >> VFS: Busy inodes after unmount of ceph. Self-destruct in 5 seconds.
>> >> Have a nice day...
>> >> 
>> >> this is with kernel 2.6.34 and ceph-client-standalone
> 
> This turned out to be an MDS bug (not replying to snap flush messages,
> leaving the inodes pinned).  The server side is fixed in the unstable
> and testing branches.  The client should still be fixed to make some
> noise about such problems.
> 
> Thanks for that test script... being able to reliably reproduce the
> problem made fixing it so much easier!
> 
> sage

thanks, verified that the message is gone.

I noticed that it takes now longer to execute the script:
test time now: 1300s
test time before: 800-900s


- Thomas


      reply	other threads:[~2010-06-08  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-05 12:24 "VFS: Busy inodes after unmount of ceph" kernel-message after umount Thomas Mueller
2010-06-07  4:10 ` Sage Weil
2010-06-07  8:33   ` Thomas Mueller
2010-06-08  5:21     ` Sage Weil
2010-06-08  8:34       ` Thomas Mueller [this message]

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='hukvba$f6o$1@dough.gmane.org' \
    --to=thomas@chaschperli.ch \
    --cc=ceph-devel@vger.kernel.org \
    /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