Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: 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 08:54:40 -0400	[thread overview]
Message-ID: <20130605125440.GA29248@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.00.1306042056350.19491@cobra.newdream.net>

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,

Josef

  reply	other threads:[~2013-06-05 12:54 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 [this message]
2013-06-05 13:36   ` Chris Mason
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=20130605125440.GA29248@localhost.localdomain \
    --to=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