From: Chris Mason <chris.mason@oracle.com>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: "Nathan A. Mourey II" <nmoureyii@ne.rr.com>,
linux-kernel@vger.kernel.org,
Linux PM mailing list <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-fsdevel@vger.kernel.org
Subject: Re: Kernel bug with btrfs on laptop with external hd and suspend and resume.
Date: Mon, 13 Feb 2012 09:41:07 -0500 [thread overview]
Message-ID: <20120213144107.GC1573@shiny> (raw)
In-Reply-To: <4F391B83.7080703@linux.vnet.ibm.com>
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
next prev parent reply other threads:[~2012-02-13 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1328990690.2464.6.camel@firefly>
2012-02-13 14:17 ` Kernel bug with btrfs on laptop with external hd and suspend and resume Srivatsa S. Bhat
2012-02-13 14:41 ` Chris Mason [this message]
2012-02-16 21:48 ` Nathan A. Mourey II
2012-02-17 13:34 ` Chris Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120213144107.GC1573@shiny \
--to=chris.mason@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nmoureyii@ne.rr.com \
--cc=rjw@sisk.pl \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).