Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756758Ab2BMOl3 (ORCPT ); Mon, 13 Feb 2012 09:41:29 -0500 Received: from acsinet15.oracle.com ([141.146.126.227]:21546 "EHLO acsinet15.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756711Ab2BMOl1 (ORCPT ); Mon, 13 Feb 2012 09:41:27 -0500 Date: Mon, 13 Feb 2012 09:41:07 -0500 From: Chris Mason To: "Srivatsa S. Bhat" Cc: "Nathan A. Mourey II" , linux-kernel@vger.kernel.org, Linux PM mailing list , "Rafael J. Wysocki" , linux-fsdevel@vger.kernel.org Subject: Re: Kernel bug with btrfs on laptop with external hd and suspend and resume. Message-ID: <20120213144107.GC1573@shiny> Mail-Followup-To: Chris Mason , "Srivatsa S. Bhat" , "Nathan A. Mourey II" , linux-kernel@vger.kernel.org, Linux PM mailing list , "Rafael J. Wysocki" , linux-fsdevel@vger.kernel.org References: <1328990690.2464.6.camel@firefly> <4F391B83.7080703@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F391B83.7080703@linux.vnet.ibm.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet21.oracle.com [156.151.31.93] X-CT-RefId: str=0001.0A090202.4F392110.00E7,ss=1,re=0.000,fgs=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1373 Lines: 33 On Mon, Feb 13, 2012 at 07:47:39PM +0530, Srivatsa S. Bhat wrote: > Adding some Cc's. > > On 02/12/2012 01:34 AM, Nathan A. Mourey II wrote: > > > I just installed the new kernel with yum update. I have an external eSATA hard drive that is > > formatted with btrfs. I closed the lid once it had booted up, I had not logged in yet. Latter I opened > > the lid and had the following message on the screen. Hope it helps. > > > > > > Feb 11 14:39:03 firefly kernel: [ 253.236050] ------------[ cut here ]------------ > > Feb 11 14:39:03 firefly kernel: [ 253.236066] kernel BUG at fs/btrfs/transaction.c:1337! This crash corresponds to: ret = btrfs_write_and_wait_transaction(trans, root); BUG_ON(ret); Which basically means we were not able to write all the metadata for the transaction (EIO during writeback). Do other messages from the kernel tell you if the crash happened before or after the suspend? What happened when the machine rebooted? Since the drive is external, I'm going to guess this is related to the device going away at the wrong time. Was it plugged in the whole time? -chris -- 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/