From: Goffredo Baroncelli <kreijack@inwind.it>
To: Kyle Manna <2bluesc@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Wang Shilong <wangsl.fnst@cn.fujitsu.com>
Subject: Re: How to remove missing device on RAID1?
Date: Tue, 20 Oct 2015 22:37:22 +0200 [thread overview]
Message-ID: <5626A602.1030106@inwind.it> (raw)
In-Reply-To: <CAM9fjH6M2yqSiqXbT4DBvHbQGq9Cdw-wzMvsYkztPSsQG=PLqQ@mail.gmail.com>
On 2015-10-20 19:24, Kyle Manna wrote:
> Hi all,
[...]
> How do I remove the missing device? I tried the `btrfs device delete
> missing /mnt` but was greeted with "ERROR: missing is not a block
> device". A quick look at that btrfs-progs git repo shows that
> `stat("missing")` is called, which of course fails since missing isn't
> a block device. Nothing other then `btrfs replace` seemed intuitive
> and all the docs mention the older command. What's the move?
In the past the device name was passed directly to the kernel, which operated in an appropriate manner if it was "missing".
The commit e3c9596d3fc8b0df647a6cbae55c2d77570de759 introduced a check so if the argument is not a real device, an error is raised.
So, now, if "missing" is passed, btrfs(-progs) stops because it is not a real device.
This change is quite old (dec 2013); however it seems that this is the first time that a complaint is raised.
>
> Thanks!
> - Kyle
>
> Versions:
> Kernel: 4.2.3-1-ARCH
> btrfs-progs: 4.2.2-1
> ᐧ
> --
> 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
>
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2015-10-20 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 17:24 How to remove missing device on RAID1? Kyle Manna
2015-10-20 19:52 ` Philip Seeger
2015-10-20 20:37 ` Goffredo Baroncelli [this message]
2015-10-20 20:58 ` Duncan
2015-10-20 21:48 ` Kyle Manna
2015-10-20 22:40 ` Henk Slager
2015-10-20 22:46 ` Henk Slager
2015-10-21 19:14 ` Kyle Manna
2015-10-21 9:54 ` Dmitry Katsubo
2015-10-21 16:40 ` Henk Slager
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=5626A602.1030106@inwind.it \
--to=kreijack@inwind.it \
--cc=2bluesc@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangsl.fnst@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).