From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Slaby Subject: Re: busy inodes -> ext3 umount crash Date: Tue, 20 Apr 2010 16:12:03 +0200 Message-ID: <4BCDB633.9040901@gmail.com> References: <4BC8A7C1.20102@gmail.com> <20100419141158.GB5439@quack.suse.cz> <4BCC69B4.2050308@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Andrew Morton , adilger@sun.com, linux-ext4@vger.kernel.org, Linux kernel mailing list , mszeredi@suse.cz To: Jan Kara Return-path: In-Reply-To: <4BCC69B4.2050308@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org 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.