From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Warnings and crash
Date: Wed, 2 Nov 2011 19:40:58 -0400 [thread overview]
Message-ID: <20111102234058.GH18900@shiny> (raw)
In-Reply-To: <20111102230231.GM12759@twin.jikos.cz>
On Thu, Nov 03, 2011 at 12:02:31AM +0100, David Sterba wrote:
> This one happened again, exactly same sequence of warnings and the crash
> at the end (same stack traces). It was in integration-scrub branch, ie.
> with all fixes on top.
>
> (I have captured sysrq-w, /proc/pid/stack of all processes and have the
> dmesg logs if anybody is interested.)
Yes, I'd like to see the logs. We need to figure out if we just failed
with enospc in a critical spot or if there are other bigger problems.
-chris
next prev parent reply other threads:[~2011-11-02 23:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 2:49 new integration-danger branch pushed out (kernel) Chris Mason
2011-11-01 9:22 ` Liu Bo
2011-11-01 10:55 ` Chris Mason
2011-11-02 2:22 ` Liu Bo
2011-11-01 10:11 ` Warnings (was: Re: new integration-danger branch pushed out (kernel)) David Sterba
2011-11-02 0:56 ` Chris Mason
2011-11-02 13:06 ` David Sterba
2011-11-01 10:28 ` Warnings: destroy inode (was: " David Sterba
2011-11-01 10:36 ` BUG at fs/btrfs/tree-log.c:3106 (Re: " David Sterba
2011-11-01 10:56 ` Chris Mason
2011-11-01 16:16 ` David Sterba
2011-11-01 16:39 ` David Sterba
2011-11-01 12:56 ` Warnings and crash David Sterba
2011-11-02 23:02 ` David Sterba
2011-11-02 23:40 ` Chris Mason [this message]
2011-11-04 0:39 ` Mitch Harder
2011-11-02 17:06 ` All green (Re: new integration-danger branch pushed out (kernel)) David Sterba
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=20111102234058.GH18900@shiny \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
/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