From: Stefan Kleijkers <stefan@unilogicnetworks.net>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: WARNING: at fs/btrfs/inode.c:2198 btrfs_orphan_commit_root+0xa8/0xc0
Date: Fri, 18 Nov 2011 20:30:51 +0100 [thread overview]
Message-ID: <4EC6B26B.1020000@unilogicnetworks.net> (raw)
In-Reply-To: <20111115192926.GB1944@localhost.localdomain>
Hello Josef,
I've two new dmesg's (ceph osd 0 and 1). Both filesystems wheren't
responding anymore. Please let me know if you need more information or
another run. Both are made with the 3.1.1 kernel and your patches
applied (the patches with the extra warning messages).
Paste:
OSD.0: http://pastebin.com/tPjMk0kH
OSD.1: http://pastebin.com/ef7A16g2
Stefan
On 11/15/2011 08:29 PM, Josef Bacik wrote:
> On Tue, Nov 15, 2011 at 08:13:43PM +0100, Stefan Kleijkers wrote:
>> Hello Josef,
>>
>> We have patched the 3.1.1 kernel with your patch and after a short
>> time one of the ceph osds crashed (core dumped) and I found this in
>> the dmesg, please let me know if that's enough information or if you
>> need more.
>>
> Yeah I was hoping for a WARN_ON() that should have shown up before that, do you
> have the entire dmesg? Thanks,
>
> Josef
next prev parent reply other threads:[~2011-11-18 19:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 10:24 WARNING: at fs/btrfs/inode.c:2198 btrfs_orphan_commit_root+0xa8/0xc0 Stefan Kleijkers
2011-11-09 14:01 ` Christian Brunner
2011-11-09 15:35 ` Josef Bacik
2011-11-10 12:13 ` Stefan Kleijkers
2011-11-14 16:03 ` Josef Bacik
2011-11-15 19:13 ` Stefan Kleijkers
2011-11-15 19:29 ` Josef Bacik
2011-11-18 19:30 ` Stefan Kleijkers [this message]
[not found] ` <4EC2C940.40605@unilogicnetworks.net>
2011-11-18 19:52 ` Josef Bacik
2011-11-26 14:14 ` Stefan Kleijkers
2011-11-26 21:21 ` Christian Brunner
2011-12-01 15:14 ` Josef Bacik
2011-12-01 20:03 ` Stefan Kleijkers
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=4EC6B26B.1020000@unilogicnetworks.net \
--to=stefan@unilogicnetworks.net \
--cc=josef@redhat.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