Re: [PATCH 0/5] Forking ext4 filesystem and JBD2

["Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>]

On 19/08/06, John McCutchan <john@johnmccutchan.com> wrote:
> On Thu, 2006-10-08 at 17:15 +0200, Michal Piotrowski wrote:
> > On 10/08/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> > > Hi,
> > >
> > > On 10/08/06, Mingming Cao <cmm@us.ibm.com> wrote:
> > > > This series of patch forkes a new filesystem, ext4, from the current
> > > > ext3 filesystem, as the code base to work on, for the big features such
> > > > as extents and larger fs(48 bit blk number) support, per our discussion
> > > > on lkml a few weeks ago.
> > >
> > > It appears after a few minutes of running
> > >
> > > #! /bin/bash
> > > while true
> > > do
> > > sudo mount -o loop -t ext3dev /home/fs-farm/ext4.img /mnt/fs-farm/ext4/
> > > sudo umount /mnt/fs-farm/ext4/
> > > done
> > >
> > > BUG: warning at /usr/src/linux-work2/fs/inotify.c:171/set_dentry_child_flags()
> > >  [<c0104006>] show_trace_log_lvl+0x58/0x152
> > >  [<c01046ad>] show_trace+0xd/0x10
> > >  [<c0104775>] dump_stack+0x19/0x1b
> > >  [<c018aa7f>] set_dentry_child_flags+0x5a/0x119
> > >  [<c018ab94>] remove_watch_no_event+0x56/0x64
> > >  [<c018ac62>] inotify_remove_watch_locked+0x12/0x34
> > >  [<c018af1b>] inotify_rm_wd+0x75/0x93
> > >  [<c018b468>] sys_inotify_rm_watch+0x40/0x58
> > >  [<c0102f15>] sysenter_past_esp+0x56/0x8d
> > > DWARF2 unwinder stuck at sysenter_past_esp+0x56/0x8d
> > > Leftover inexact backtrace:
> > >  [<c01046ad>] show_trace+0xd/0x10
> > >  [<c0104775>] dump_stack+0x19/0x1b
> > >  [<c018aa7f>] set_dentry_child_flags+0x5a/0x119
> > >  [<c018ab94>] remove_watch_no_event+0x56/0x64
> > >  [<c018ac62>] inotify_remove_watch_locked+0x12/0x34
> > >  [<c018af1b>] inotify_rm_wd+0x75/0x93
> > >  [<c018b468>] sys_inotify_rm_watch+0x40/0x58
> > >  [<c0102f15>] sysenter_past_esp+0x56/0x8d
> > > kjournald2 starting.  Commit interval 5 seconds
> >
> > Definitely it's an inotify bug. I have checked this with other file systems.
>
> I just ran your loop of mounting/unmounting a fs for over an hour and I
> can't reproduce this.

I can reproduce this in a few minutes.

ls -sh /home/fs-farm/
razem 3,6G
513M ext2.img  513M ext4.img  513M reiser3.img  513M xfs.img
513M ext3.img  513M jfs.img   513M reiser4.img

#! /bin/bash

m_fs() {
   sudo mount -o loop -t ext2 /home/fs-farm/ext2.img /mnt/fs-farm/ext2/
   sudo mount -o loop -t ext3 /home/fs-farm/ext3.img /mnt/fs-farm/ext3/
   sudo mount -o loop -t ext3dev /home/fs-farm/ext4.img /mnt/fs-farm/ext4/
   sudo mount -o loop -t reiserfs /home/fs-farm/reiser3.img
/mnt/fs-farm/reiser3/
   sudo mount -o loop -t reiser4 /home/fs-farm/reiser4.img
/mnt/fs-farm/reiser4/
   sudo mount -o loop -t xfs /home/fs-farm/xfs.img /mnt/fs-farm/xfs/
   sudo mount -o loop -t jfs /home/fs-farm/jfs.img /mnt/fs-farm/jfs/
}

u_fs() {
   sudo umount /mnt/fs-farm/ext2/
   sudo umount /mnt/fs-farm/ext3/
   sudo umount /mnt/fs-farm/ext4/
   sudo umount /mnt/fs-farm/reiser3/
   sudo umount /mnt/fs-farm/reiser4/
   sudo umount /mnt/fs-farm/xfs/
   sudo umount /mnt/fs-farm/jfs/
}

while true
do
m_fs
u_fs
done

mount
[..]
/dev/sda3 on /home type ext3 (rw)

http://www.stardust.webpages.pl/files/o_bugs/mm-config

> --
> John McCutchan <john@johnmccutchan.com>

Regards,
Michal

--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/