linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Marc MERLIN <marc@merlins.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: BUG: unable to handle kernel NULL pointer rcu_string_strdup.constprop.63+0x14/0x48
Date: Wed, 29 Aug 2012 10:35:01 -0400	[thread overview]
Message-ID: <20120829143501.GB2272@localhost.localdomain> (raw)
In-Reply-To: <20120824174233.GB18380@merlins.org>

On Fri, Aug 24, 2012 at 11:42:33AM -0600, Marc MERLIN wrote:
> With 3.5.2, I created 5 dm-crypted devices from 5 drives.
> I created a raid0 btrfs filesystem and wrote stuff to it.
> One drive died.
> 

I fixed this in btrfs-next, please build that and verify it fixes your problem.
Thanks,

Josef

      parent reply	other threads:[~2012-08-29 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 17:42 BUG: unable to handle kernel NULL pointer rcu_string_strdup.constprop.63+0x14/0x48 Marc MERLIN
2012-08-29 14:28 ` Marc MERLIN
2012-08-29 14:35 ` Josef Bacik [this message]

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=20120829143501.GB2272@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marc@merlins.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;
as well as URLs for NNTP newsgroup(s).