From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753072Ab2CIKz5 (ORCPT ); Fri, 9 Mar 2012 05:55:57 -0500 Received: from twin.jikos.cz ([89.185.236.188]:40744 "EHLO twin.jikos.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751209Ab2CIKzz (ORCPT ); Fri, 9 Mar 2012 05:55:55 -0500 Date: Fri, 9 Mar 2012 11:55:37 +0100 From: David Sterba To: Liu Bo Cc: Jacek Luczak , dave@jikos.cz, linux-btrfs , LKML , josef@redhat.com Subject: Re: kernel BUG at fs/btrfs/delayed-inode.c:1466! Message-ID: <20120309105537.GG4334@twin.jikos.cz> Reply-To: dave@jikos.cz Mail-Followup-To: Liu Bo , Jacek Luczak , dave@jikos.cz, linux-btrfs , LKML , josef@redhat.com References: <20120308155211.GF4334@twin.jikos.cz> <4F595D6D.6080809@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F595D6D.6080809@cn.fujitsu.com> User-Agent: Mutt/1.4.2.2i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 09, 2012 at 09:31:25AM +0800, Liu Bo wrote: > > There were quite many things happening in the system at that time. > > Can't really tell what could trigger this. > > > > Complete logs: http://91.234.146.107/~difrost/logs/tampere_log.gz > > > So are these warnings based on the latest upstream of btrfs? No, from the log it's 3.2.7, so it does not conain the patch "increase the global block reserve estimates" the log shows lots of messages Mar 8 13:36:37 kernel: use_block_rsv: 7 callbacks suppressed Mar 8 13:36:37 kernel: ------------[ cut here ]------------ Mar 8 13:36:37 kernel: WARNING: at fs/btrfs/extent-tree.c:5985 btrfs_alloc_free_block+0xc5/0x292 [btrfs]() ... Mar 8 13:36:37 kernel: [] ? btrfs_alloc_free_block+0xc5/0x292 [btrfs] Mar 8 13:36:37 kernel: [] ? warn_slowpath_common+0x78/0x8d Mar 8 13:36:37 kernel: [] ? btrfs_alloc_free_block+0xc5/0x292 [btrfs] Mar 8 13:36:37 kernel: [] ? btrfs_item_offset+0x2c/0x61 [btrfs] Mar 8 13:36:37 kernel: [] ? leaf_space_used+0x86/0xb5 [btrfs] Mar 8 13:36:39 kernel: [] ? split_leaf+0x2d9/0x632 [btrfs] Mar 8 13:36:39 kernel: [] ? btrfs_search_slot+0x6c1/0x75a [btrfs] Mar 8 13:36:40 kernel: [] ? btrfs_insert_empty_items+0x61/0xab [btrfs] Mar 8 13:36:41 kernel: [] ? insert_inline_extent+0xea/0x2d4 [btrfs] Mar 8 13:36:41 kernel: [] ? cow_file_range_inline+0x123/0x163 [btrfs] ... so there is probably other problem in reservations and it just blew up during the unlink call. david