From: Jiri Slaby <jirislaby@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
adilger@sun.com, linux-ext4@vger.kernel.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
mszeredi@suse.cz
Subject: Re: busy inodes -> ext3 umount crash
Date: Tue, 20 Apr 2010 16:12:03 +0200 [thread overview]
Message-ID: <4BCDB633.9040901@gmail.com> (raw)
In-Reply-To: <4BCC69B4.2050308@gmail.com>
On 04/19/2010 04:33 PM, Jiri Slaby wrote:
> The trigger for busy inodes is as simple as (I=initialization done only
> once):
> I> # dd if=/dev/zero of=/dev/shm/ext3 bs=1024 count=1 seek=$((100*1024))
> I> # mkfs.ext3 -m 0 /dev/shm/ext3
> # mount -oloop /dev/shm/ext3 /mnt/c
> # umount /mnt/c
> # dmesg|tail
> VFS: Busy inodes after unmount of loop0. Self-destruct in 5 seconds.
> Have a nice day...
>
> (The printk time varies -- this sequence really suffices.)
Well, this happens only after gnome-session is started and it's fuzzy --
sometimes it happens, sometimes not. I didn't find 100% trigger yet.
>> So if you can easily reproduce
>> the "busy inodes" message then I'd start with debugging that one. Do you
>> see it also with vanilla kernels?
Vanilla seems not to be affected. It's in next/master already though
(2603ecd9). I'll investigate it further later.
next prev parent reply other threads:[~2010-04-20 14:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 18:09 busy inodes -> ext3 umount crash Jiri Slaby
2010-04-19 14:11 ` Jan Kara
2010-04-19 14:33 ` Jiri Slaby
2010-04-20 14:12 ` Jiri Slaby [this message]
2010-04-20 15:28 ` Jan Kara
2010-04-21 15:16 ` Jiri Slaby
2010-04-21 15:24 ` Eric Paris
2010-04-21 15:47 ` Jiri Slaby
2010-04-21 16:00 ` Eric Paris
2010-04-21 21:25 ` Eric Paris
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=4BCDB633.9040901@gmail.com \
--to=jirislaby@gmail.com \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).