From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomasz Chmielewski Subject: flood of btrfs WARNINGs in dmesg Date: Mon, 04 Oct 2010 15:19:41 +0200 Message-ID: <4CA9D46D.6060309@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 To: linux-btrfs@vger.kernel.org Return-path: List-ID: With 2.6.35.x, I saw warnings like below in dmesg. With 2.6.36-rc6, I even had a flood of them. Is it something to worry about? What causes it? You can see more of these under http://www.virtall.com/files/dmesg-btrfs-flood.txt [74921.736528] ------------[ cut here ]------------ [74921.736597] WARNING: at /home/kernel-ppa/COD/linux/fs/fs-writeback.c:87 __mark_inode_dirty+0x217/0x250() [74921.736604] Hardware name: Bochs [74921.736606] Dirtiable inode bdi default != sb bdi btrfs [74921.736611] Modules linked in: btrfs zlib_deflate crc32c libcrc32c lp parport psmouse serio_raw i2c_piix4 virtio_net floppy virtio_blk virtio_pci virtio_ring virtio [74921.736635] Pid: 22522, comm: rsync Not tainted 2.6.36-020636rc6-generic #201009291126 [74921.736638] Call Trace: [74921.736649] [] ? __mark_inode_dirty+0x217/0x250 [74921.736678] [] warn_slowpath_common+0x90/0xc0 [74921.736683] [] warn_slowpath_fmt+0x6e/0x70 [74921.736712] [] ? __btrfs_end_transaction+0x128/0x210 [btrfs] [74921.736727] [] ? btrfs_end_transaction+0x10/0x20 [btrfs] [74921.736744] [] ? btrfs_dirty_inode+0x7c/0x120 [btrfs] [74921.736781] [] ? _raw_spin_lock+0xe/0x20 [74921.736785] [] __mark_inode_dirty+0x217/0x250 [74921.736804] [] btrfs_setattr+0x78/0xb0 [btrfs] [74921.736814] [] notify_change+0x170/0x2d0 [74921.736824] [] utimes_common+0xdb/0x1a0 [74921.736829] [] do_utimes+0xaa/0x110 [74921.736833] [] sys_futimesat+0x36/0xd0 [74921.736837] [] sys_utimes+0x19/0x20 [74921.736854] [] system_call_fastpath+0x16/0x1b [74921.736870] ---[ end trace 7c45187572db04d2 ]--- -- Tomasz Chmielewski http://wpkg.org