Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Lukas Pirl <btrfs@lukas-pirl.de>
To: Alexander Fougner <fougner89@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 4.2.6: livelock in recovery (free_reloc_roots)?
Date: Sat, 21 Nov 2015 22:38:56 +1300	[thread overview]
Message-ID: <56503BB0.3070702@lukas-pirl.de> (raw)
In-Reply-To: <565032DA.5010602@gmail.com>

On 11/21/2015 10:01 PM, Alexander Fougner wrote as excerpted:
> This is fixed in btrfs-progs 4.3.1, that allows you to delete a
> device again by the 'missing' keyword.

Thanks Alexander! I just found the thread reporting the bug but not the
patch with the corresponding btrfs-tools version it was merged in.

Lukas

  reply	other threads:[~2015-11-26  2:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20  9:04 4.2.6: livelock in recovery (free_reloc_roots)? Lukas Pirl
2015-11-21  0:37 ` Lukas Pirl
2015-11-21  7:16   ` Duncan
2015-11-21  9:01     ` Alexander Fougner
2015-11-21  9:38       ` Lukas Pirl [this message]
2015-11-21 11:18     ` Lukas Pirl
2016-03-02 12:56 ` Still in 4.4.0: livelock in recovery (free_reloc_roots) Lukas Pirl

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=56503BB0.3070702@lukas-pirl.de \
    --to=btrfs@lukas-pirl.de \
    --cc=fougner89@gmail.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