On Tue 20-04-10 16:12:03, Jiri Slaby wrote: > 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. Hmph - maybe something in inotify? Dunno... > >> 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. Do you mean it's in today's linux-next but not in Linus' tree? Honza -- Jan Kara <jack@xxxxxxx> SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
