Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965785Ab0GPO7V (ORCPT ); Fri, 16 Jul 2010 10:59:21 -0400 Received: from mail.fem.tu-ilmenau.de ([141.24.101.79]:40825 "EHLO mail.fem.tu-ilmenau.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965765Ab0GPO7T (ORCPT ); Fri, 16 Jul 2010 10:59:19 -0400 From: Johannes Hirte To: Dave Chinner Subject: Re: kernel BUG at fs/btrfs/extent-tree.c:1353 Date: Fri, 16 Jul 2010 16:59:46 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.35-rc4-btrfs-debug; KDE/4.4.5; i686; ; ) Cc: Chris Mason , linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org, zheng.yan@oracle.com, Jens Axboe , linux-fsdevel@vger.kernel.org References: <201007081627.24654.johannes.hirte@fem.tu-ilmenau.de> <20100715001104.GF30737@dastard> <201007152014.52924.johannes.hirte@fem.tu-ilmenau.de> In-Reply-To: <201007152014.52924.johannes.hirte@fem.tu-ilmenau.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201007161659.48663.johannes.hirte@fem.tu-ilmenau.de> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 5008 Lines: 104 Am Donnerstag 15 Juli 2010, 20:14:51 schrieb Johannes Hirte: > Am Donnerstag 15 Juli 2010, 02:11:04 schrieb Dave Chinner: > > On Wed, Jul 14, 2010 at 05:25:23PM +0200, Johannes Hirte wrote: > > > Am Donnerstag 08 Juli 2010, 16:31:09 schrieb Chris Mason: > > > I'm not sure if btrfs is to blame for this error. After the errors I > > > switched to XFS on this system and got now this error: > > > > > > ls -l .kde4/share/apps/akregator/data/ > > > ls: cannot access .kde4/share/apps/akregator/data/feeds.opml: Structure > > > needs cleaning > > > total 4 > > > ?????????? ? ? ? ? ? feeds.opml > > > > What is the error reported in dmesg when the XFS filesytem shuts down? > > Nothing. I double checked the logs. There are only the messages when > mounting the filesystem. No other errors are reported than the > inaccessible file and the output from xfs_check. I'm running now a kernel with more debug options enabled and got this: [ 6794.810935] [ 6794.810941] ================================= [ 6794.810955] [ INFO: inconsistent lock state ] [ 6794.810966] 2.6.35-rc4-btrfs-debug #7 [ 6794.810975] --------------------------------- [ 6794.810984] inconsistent {RECLAIM_FS-ON-W} -> {IN-RECLAIM_FS-W} usage. [ 6794.810996] kswapd0/361 [HC0[0]:SC0[0]:HE1:SE1] takes: [ 6794.811006] (&(&ip->i_iolock)->mr_lock#2){++++?+}, at: [] xfs_ilock+0x22/0x67 [ 6794.811039] {RECLAIM_FS-ON-W} state was registered at: [ 6794.811046] [] mark_held_locks+0x42/0x5e [ 6794.811046] [] lockdep_trace_alloc+0x99/0xb0 [ 6794.811046] [] __alloc_pages_nodemask+0x6a/0x4a1 [ 6794.811046] [] __page_cache_alloc+0x11/0x13 [ 6794.811046] [] grab_cache_page_write_begin+0x47/0x81 [ 6794.811046] [] block_write_begin_newtrunc+0x2e/0x9c [ 6794.811046] [] block_write_begin+0x23/0x5d [ 6794.811046] [] xfs_vm_write_begin+0x26/0x28 [ 6794.811046] [] generic_file_buffered_write+0xb5/0x1bd [ 6794.811046] [] xfs_file_aio_write+0x40e/0x66d [ 6794.811046] [] do_sync_write+0x8b/0xc6 [ 6794.811046] [] vfs_write+0x77/0xa4 [ 6794.811046] [] sys_write+0x3c/0x5e [ 6794.811046] [] sysenter_do_call+0x12/0x36 [ 6794.811046] irq event stamp: 141369 [ 6794.811046] hardirqs last enabled at (141369): [] _raw_spin_unlock_irqrestore+0x36/0x5b [ 6794.811046] hardirqs last disabled at (141368): [] _raw_spin_lock_irqsave+0x14/0x68 [ 6794.811046] softirqs last enabled at (141300): [] __do_softirq+0xfe/0x10d [ 6794.811046] softirqs last disabled at (141295): [] do_softirq+0x2f/0x47 [ 6794.811046] [ 6794.811046] other info that might help us debug this: [ 6794.811046] 2 locks held by kswapd0/361: [ 6794.811046] #0: (shrinker_rwsem){++++..}, at: [] shrink_slab+0x25/0x13f [ 6794.811046] #1: (&xfs_mount_list_lock){++++.-}, at: [] xfs_reclaim_inode_shrink+0x2a/0xe8 [ 6794.811046] [ 6794.811046] stack backtrace: [ 6794.811046] Pid: 361, comm: kswapd0 Not tainted 2.6.35-rc4-btrfs-debug #7 [ 6794.811046] Call Trace: [ 6794.811046] [] ? printk+0xf/0x17 [ 6794.811046] [] valid_state+0x134/0x142 [ 6794.811046] [] mark_lock+0xd0/0x1e9 [ 6794.811046] [] ? check_usage_forwards+0x0/0x5f [ 6794.811046] [] __lock_acquire+0x374/0xc80 [ 6794.811046] [] ? sched_clock_local+0x12/0x121 [ 6794.811046] [] ? sched_clock_cpu+0x122/0x133 [ 6794.811046] [] lock_acquire+0x5f/0x76 [ 6794.811046] [] ? xfs_ilock+0x22/0x67 [ 6794.811046] [] down_write_nested+0x32/0x63 [ 6794.811046] [] ? xfs_ilock+0x22/0x67 [ 6794.811046] [] xfs_ilock+0x22/0x67 [ 6794.811046] [] xfs_ireclaim+0x98/0xbb [ 6794.811046] [] ? up_write+0x16/0x2b [ 6794.811046] [] xfs_reclaim_inode+0x1a7/0x1b1 [ 6794.811046] [] xfs_inode_ag_walk+0x77/0xbc [ 6794.811046] [] ? xfs_reclaim_inode+0x0/0x1b1 [ 6794.811046] [] xfs_inode_ag_iterator+0x52/0x99 [ 6794.811046] [] ? xfs_reclaim_inode_shrink+0x2a/0xe8 [ 6794.811046] [] ? xfs_reclaim_inode+0x0/0x1b1 [ 6794.811046] [] xfs_reclaim_inode_shrink+0x4b/0xe8 [ 6794.811046] [] shrink_slab+0xd2/0x13f [ 6794.811046] [] kswapd+0x37d/0x4e9 [ 6794.811046] [] ? autoremove_wake_function+0x0/0x2f [ 6794.811046] [] ? kswapd+0x0/0x4e9 [ 6794.811046] [] kthread+0x60/0x65 [ 6794.811046] [] ? kthread+0x0/0x65 [ 6794.811046] [] kernel_thread_helper+0x6/0x10 Don't know if this is related to the problem. regards, Johannes -- 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/