All of lore.kernel.org
 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: Mon, 7 Jun 2010 08:33:09 +0000 (UTC)	[thread overview]
Message-ID: <huias5$pf4$1@dough.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.1006062109410.14891@cobra.newdream.net

Am Sun, 06 Jun 2010 21:10:28 -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 one is new.  Can you say a bit more about what workload induced the
> crash?  Or better yet, are you able to reproduce it?
> 

yes, i get the message every time i run the test and do the umount. the 
system is debian squeeze with 4GB of RAM and 2.6.34 kernel from 
experimental repo. cannot test it on centos5 right now. 


what the script does:
- mkdir snaptest-2; cd snaptest-2
- create 100 dirs with 1 textfile in it
- mkdir .snap/test-1
- create 100 dirs with 1 textfile in it
- for every subdir create a snapshot (mkdir $i/.snap/snaptest) and then 
create 10 textfiles
- mkdir .snap/test-2
- mkdir copysnap1; cp -R .snap/test-1 copysnap1/
- mkdir .snap/test-3
- rm -Rf ./*
- umount

(http://github.com/vinzent/ceph-testsuite/blob/master/tests/snaptest-2)

- Thomas


  reply	other threads:[~2010-06-07  8:33 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 [this message]
2010-06-08  5:21     ` Sage Weil
2010-06-08  8:34       ` Thomas Mueller

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='huias5$pf4$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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.