Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965216AbWILQgE (ORCPT ); Tue, 12 Sep 2006 12:36:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965228AbWILQgE (ORCPT ); Tue, 12 Sep 2006 12:36:04 -0400 Received: from nf-out-0910.google.com ([64.233.182.190]:37766 "EHLO nf-out-0910.google.com") by vger.kernel.org with ESMTP id S965216AbWILQgD (ORCPT ); Tue, 12 Sep 2006 12:36:03 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:mime-version:content-type:content-disposition:user-agent; b=WOpkh5Nhmfp1PBV6DPndtyUIE3l97K6wr6SDeTfrw1pvgKSTbKb6CJy6ieVUvXkF5XObaqW/87sNzZIsY/7I1Rj1VoJq/D7GSHg4Wx58T/HiUX2shi8BMhdKGUubEqKLZVXIxFHdSaNWbb9X+2L301phFOMDpWM1Hn57XdFl8qA= Date: Tue, 12 Sep 2006 18:36:00 +0200 From: Luca To: xfs-masters@oss.sgi.com Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com Subject: XFS: lockdep warning: BUG: held lock freed! Message-ID: <20060912163600.GA2948@dreamland.darkstar.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3527 Lines: 85 Hi, I see that this error has alredy been observed with 2.6.17-mm; I'm running kernel 2.6.18-rc5 (x86, UP, with PREEMPT) and may have additional information. In my case the FS was affected by 2.6.17 directory corruption (I forgot to run xfs_repair on this machine); after the FS was shut down I rebooted the machine (with init=/bin/bash, rootfs on ext2, so it was not affected) and mounted XFS partition read-only to recover the log. I tried to reproduce with "simple" crashes (i.e. write a file and reboot, I don't want to trash the FS too much ;)) without success, so the error may be related to directory corruption. lockdep message: SGI XFS with no debug enabled XFS mounting filesystem hda8 Starting XFS recovery on filesystem: hda8 (logdev: internal) ========================= [ BUG: held lock freed! ] ------------------------- mount/290 is freeing memory ef798b70-ef798baf, with a lock still held there! (&(&ip->i_lock)->mr_lock){--..}, at: [] xfs_ilock+0x7d/0xb0 [xfs] 3 locks held by mount/290: #0: (&type->s_umount_key#14){--..}, at: [] sget+0x19c/0x320 #1: (&(&ip->i_iolock)->mr_lock){--..}, at: [] xfs_ilock+0x9e/0xb0 [xfs] #2: (&(&ip->i_lock)->mr_lock){--..}, at: [] xfs_ilock+0x7d/0xb0 [xfs] stack backtrace: [] show_trace_log_lvl+0x176/0x1a0 [] show_trace+0x12/0x20 [] dump_stack+0x19/0x20 [] debug_check_no_locks_freed+0x169/0x180 [] __init_rwsem+0x21/0x60 [] xfs_inode_lock_init+0x25/0x80 [xfs] [] xfs_iget+0x18a/0x5b8 [xfs] [] xlog_recover_process_iunlinks+0x316/0x500 [xfs] [] xlog_recover_finish+0x2be/0x380 [xfs] [] xfs_log_mount_finish+0x37/0x50 [xfs] [] xfs_mountfs+0xe50/0x1020 [xfs] [] xfs_ioinit+0x29/0x40 [xfs] [] xfs_mount+0x65c/0xa10 [xfs] [] vfs_mount+0x25/0x30 [xfs] [] xfs_fs_fill_super+0x76/0x1e0 [xfs] [] get_sb_bdev+0xec/0x130 [] xfs_fs_get_sb+0x21/0x30 [xfs] [] vfs_kern_mount+0x40/0xa0 [] do_kern_mount+0x36/0x50 [] do_mount+0x22e/0x610 [] sys_mount+0x6f/0xb0 [] syscall_call+0x7/0xb [] 0xa7ef00be [] show_trace+0x12/0x20 [] dump_stack+0x19/0x20 [] debug_check_no_locks_freed+0x169/0x180 [] __init_rwsem+0x21/0x60 [] xfs_inode_lock_init+0x25/0x80 [xfs] [] xfs_iget+0x18a/0x5b8 [xfs] [] xlog_recover_process_iunlinks+0x316/0x500 [xfs] [] xlog_recover_finish+0x2be/0x380 [xfs] [] xfs_log_mount_finish+0x37/0x50 [xfs] [] xfs_mountfs+0xe50/0x1020 [xfs] [] xfs_ioinit+0x29/0x40 [xfs] [] xfs_mount+0x65c/0xa10 [xfs] [] vfs_mount+0x25/0x30 [xfs] [] xfs_fs_fill_super+0x76/0x1e0 [xfs] [] get_sb_bdev+0xec/0x130 [] xfs_fs_get_sb+0x21/0x30 [xfs] [] vfs_kern_mount+0x40/0xa0 [] do_kern_mount+0x36/0x50 [] do_mount+0x22e/0x610 [] sys_mount+0x6f/0xb0 [] syscall_call+0x7/0xb Ending XFS recovery on filesystem: hda8 (logdev: internal) Luca -- Home: http://kronoz.cjb.net Runtime error 6D at f000:a12f : user incompetente - 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/