From: Chris Mason <chris.mason@fusionio.com>
To: Josef Bacik <jbacik@fusionio.com>, Sage Weil <sage@inktank.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: v3.9 bug at /fs/btrfs/free-space-cache.c:1567 after powercycle
Date: Wed, 5 Jun 2013 09:36:50 -0400 [thread overview]
Message-ID: <20130605133650.4088.67669@localhost.localdomain> (raw)
In-Reply-To: <20130605125440.GA29248@localhost.localdomain>
Quoting Josef Bacik (2013-06-05 08:54:40)
> On Tue, Jun 04, 2013 at 09:59:05PM -0600, Sage Weil wrote:
> > Hi-
> >
> > I'm pretty reliably triggering the following bug after powercycling an
> > active btrfs + ceph workload and then trying to remount. Is this a known
> > issue?
> >
>
> Yeah sorry it's fixed in 3.10, I really need to send the patch back to stable.
> Thanks,
Do we need more than:
commit b50c6e250ef91313518dbca96663578237ba8d3c
Author: Josef Bacik <jbacik@fusionio.com>
Date: Thu Apr 25 15:55:30 2013 -0400
Btrfs: deal with free space cache errors while replaying log
commit 09a2a8f96e3009273bed1833b3f210e2c68728a5
Author: Josef Bacik <jbacik@fusionio.com>
Date: Fri Apr 5 16:51:15 2013 -0400
Btrfs: fix bad extent logging
commit cc95bef635a649d595cf8d1cd4fcff5b6bf13023
Author: Josef Bacik <jbacik@fusionio.com>
Date: Thu Apr 4 14:31:27 2013 -0400
Btrfs: log ram bytes properly
-chris
next prev parent reply other threads:[~2013-06-05 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 3:59 v3.9 bug at /fs/btrfs/free-space-cache.c:1567 after powercycle Sage Weil
2013-06-05 12:54 ` Josef Bacik
2013-06-05 13:36 ` Chris Mason [this message]
2013-06-05 15:08 ` Sage Weil
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=20130605133650.4088.67669@localhost.localdomain \
--to=chris.mason@fusionio.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sage@inktank.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