Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Rasmus Abrahamsen <me@rasmusa.net>
To: linux-btrfs@vger.kernel.org
Subject: delete missing /dev/sdd which is now added as /dev/sdd1
Date: Wed, 13 Aug 2014 07:35:49 +0200	[thread overview]
Message-ID: <53EAF935.4040605@rasmusa.net> (raw)

I have a BTRFS mirrored raid on three disks: 500 GB, 1000 GB, 1500 GB.
The 1500 GB is going bad.

I bought a 4000 GB and wanted to make a 1500 GB and also a 2500 GB
partition. By mistake I made a 1.5 GB and did not realize it until much
later.

I added the 1.5 GB to my raid and tried removing the 1500 GB, I
obviously coudn't. I ended up turning off the machine and unplugging the
1500 GB and tried the btrfs delete missing, but that failed too because
delete missing needs new space available otherwise it will fail.

So I reformatted my 1500 GB and added it to the raid again, it showed
up... but twice... I had one empty /dev/sdd and one non-empty /dev/sdd.

I figured I could fix it by removing and formatting it again, this time
creating a partition using fdisk, it would change the device to
/dev/sdd1.

I added the /dev/sdd1 to my raid and deleted the missing. Now the
/dev/sdd does not show up anymore and I have a /dev/sdd1. But I still
have the **** Some devices missing and the command btrfs delete missing
/mnt does not actually do anything. I tried btrfs delete /dev/sdd /mnt
but it said that /dev/sdd was busy.

How can I tell btrfs that it is NOT the same drive?

Here is a screenshot from the machine:
https://www.dropbox.com/s/f33l4ncsni7wd0s/2014-08-13%2007.31.42.jpg

I figured I could somehow change the /dev/ name, but I am not sure how.

Rasmus

             reply	other threads:[~2014-08-13  5:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-13  5:35 Rasmus Abrahamsen [this message]
2014-08-13 14:51 ` delete missing /dev/sdd which is now added as /dev/sdd1 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

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=53EAF935.4040605@rasmusa.net \
    --to=me@rasmusa.net \
    --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