From: Chris Dunlop <chris@onthe.net.au>
To: Wido den Hollander <wido@widodh.nl>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Bug #563 - osd: btrfs, warning at inode.c ( btrfs_orphan_commit_root )
Date: Mon, 7 Feb 2011 17:23:06 +1100 [thread overview]
Message-ID: <20110207062306.GB25062@onthe.net.au> (raw)
In-Reply-To: <1296830292.2408.0.camel@wido-desktop>
On Fri, Feb 04, 2011 at 03:38:12PM +0100, Wido den Hollander wrote:
> On Fri, 2011-02-04 at 19:48 +1100, Chris Dunlop wrote:
>>
>> http://tracker.newdream.net/issues/563
>>
>> I see this bug was closed 5 days ago. Which commit[s] closed it? I'm
>> getting it on ceph-client 9aae8fa + btrfs-work bacae12 when I do a
>> mkcephfs on 3 x 2 GB OSDs, e.g.:
>
> From what I've heard they are working on it upstream (btrfs). Not sure
> what the state is though.
They're not waiting still for Sage?
From your initial report at the top of the ticket:
#btrfs
20:00 < widodh> I've just upgraded to 2.6.37-rc1 to test Ceph, but I'm seeing this right now in my dmesg:
http://pastebin.com/3HiGiNgy ( inode.c / btrfs_orphan_commit_root )
20:01 < josef> hrm looks like sage screwed something up with async commit
20:02 < widodh> aha, file it over there then?
20:03 < josef> well tell sage about it, he's the one who wrote the code so he'll probably be able to fix it quicker
20:03 < widodh> yes, sure. I thought it was a btrfs bug, that's why I came along here
20:03 < widodh> thanks!
20:05 < josef> well it is a bug in btrfs, but he will be able to fix it quicker than i will
I'll see what the linux-btrfs mailing list has to say about it...
Cheers,
Chris.
next prev parent reply other threads:[~2011-02-07 6:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 8:48 Bug #563 - osd: btrfs, warning at inode.c ( btrfs_orphan_commit_root ) Chris Dunlop
2011-02-04 14:38 ` Wido den Hollander
2011-02-07 6:23 ` Chris Dunlop [this message]
2011-02-07 6:31 ` WARNING: at fs/btrfs/inode.c:2143 btrfs_orphan_commit_root+0x7f/0x9b Chris Dunlop
2011-02-07 7:39 ` Chris Dunlop
2011-02-08 7:37 ` Chris Dunlop
2011-02-08 15:19 ` Sage Weil
2011-02-09 3:58 ` Chris Dunlop
2011-02-04 17:22 ` Bug #563 - osd: btrfs, warning at inode.c ( btrfs_orphan_commit_root ) Sage Weil
2011-02-07 6:24 ` Chris Dunlop
2011-02-07 7:38 ` Chris Dunlop
2011-02-07 10:27 ` Smets, Jan (Jan)
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=20110207062306.GB25062@onthe.net.au \
--to=chris@onthe.net.au \
--cc=ceph-devel@vger.kernel.org \
--cc=wido@widodh.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.