From: Rasmus Abrahamsen <me@rasmusa.net>
To: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: delete missing /dev/sdd which is now added as /dev/sdd1
Date: Thu, 14 Aug 2014 07:21:36 +0200 [thread overview]
Message-ID: <1407993696.3962313.152559325.65391308@webmail.messagingengine.com> (raw)
In-Reply-To: <C14B310E-5F2B-4762-884B-AA11108373D3@colorremedies.com>
Wow, such a long and detailed message. Thank you so much for taking the
time to do this.
Well, to be honest, I am starting to like the idea of starting over,
although it will be a pain.
Besides, I would have to wait for any distro to make a live disk with
the new btrfs version because my linux partition is also on that raid.
I also learned that "btrfs delete missing" should only be used if the
drive is gone forever, not to force remove it because of a mistake I did
myself (tried to replace it with the 1,5 GB partition).
On Thu, Aug 14, 2014, at 04:06 AM, Chris Murphy wrote:
>
> On Aug 13, 2014, at 5:19 PM, Duncan <1i5t5.duncan@cox.net> wrote:
> >
> > 2) Wait for the patch to make it into kernel 3.17 and go from there.
>
> Based on integration right now it looks like a lot of stuff.
>
>
> > 3) Go read the list and find and cherrypick that patch, then rebuild with
> > it included, and go from there.
>
> Could be this one:
> http://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git/patch/?id=0c414ebcd5ba515b58249099619a5d9dbcc1a3b8
>
>
> Chris Murphy
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-08-14 5:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 5:35 delete missing /dev/sdd which is now added as /dev/sdd1 Rasmus Abrahamsen
2014-08-13 14:51 ` Marc MERLIN
2014-08-13 15:36 ` Rasmus Abrahamsen
2014-08-13 23:19 ` Duncan
2014-08-14 2:06 ` Chris Murphy
2014-08-14 5:21 ` Rasmus Abrahamsen [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=1407993696.3962313.152559325.65391308@webmail.messagingengine.com \
--to=me@rasmusa.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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