From: Rasmus Abrahamsen <me@rasmusa.net>
To: Marc MERLIN <marc@merlins.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: delete missing /dev/sdd which is now added as /dev/sdd1
Date: Wed, 13 Aug 2014 17:36:06 +0200 [thread overview]
Message-ID: <1407944166.3763056.152323965.0FFD88B6@webmail.messagingengine.com> (raw)
In-Reply-To: <20140813145155.GA20611@merlins.org>
/mnt is the mount point. I now did the following
dd if=/dev/zero of=/dev/sdd
Finally, btrfs does not recognize the partition as part of my raid
anymore, but what's worse is that it now tells me that two missing
devices is a no go, so I cannot mount it as anything but read-only. All
the data is there, /dev/sdd1 was never used and /dev/sdd was the
originally missing one. Mounting as read-only prevents you from adding
devices.
I guess I have to start over... At least the old pool is still readable.
Sucks that I have to rebuild it though. I guess there is no way to keep
my snapshots without having them fill their full size.
On Wed, Aug 13, 2014, at 04:51 PM, Marc MERLIN wrote:
> On Wed, Aug 13, 2014 at 07:35:49AM +0200, Rasmus Abrahamsen wrote:
> > 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.
>
> Have you tried
> btrfs device delete missing /mnt/mountpoint ?
>
> Marc
> --
> "A mouse is a device used to point at the xterm you want to type in" -
> A.S.R.
> Microsoft is to operating systems ....
> .... what McDonalds is to gourmet
> cooking
> Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2014-08-13 15:36 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 [this message]
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=1407944166.3763056.152323965.0FFD88B6@webmail.messagingengine.com \
--to=me@rasmusa.net \
--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