From: Andrei Borzenkov <arvidjaar@gmail.com>
To: "Jakob Schöttl" <jschoett@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Cannot 'mount -o degraded /dev/replacement' after a replace
Date: Sat, 9 Feb 2019 18:36:37 +0300 [thread overview]
Message-ID: <b89f4970-c750-81d9-5eec-44a0ff14c4e1@gmail.com> (raw)
In-Reply-To: <2efee604-e44c-b00b-2ea8-d13ebc8c6355@gmail.com>
09.02.2019 13:36, Jakob Schöttl пишет:
> btrfs filesystem show # to get devid of device 2
Funny because for me it just says "Some devices missing" without giving
exact device id. May be has been fixed in recent versions but for a long
time it really annoyed me.
OK, when I just unplug device it does not say it - but it also does not
say *which* device is missing, it happily continues to show old device
names at the time of mount, be they actually present or not.
I always wondered how users are supposed to know which device to replace.
next prev parent reply other threads:[~2019-02-09 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 10:36 Cannot 'mount -o degraded /dev/replacement' after a replace Jakob Schöttl
2019-02-09 12:16 ` Qu Wenruo
2019-02-09 13:45 ` Jakob Schöttl
2019-02-09 15:32 ` Andrei Borzenkov
2019-02-09 15:57 ` Jakob Schöttl
2019-02-09 15:36 ` Andrei Borzenkov [this message]
2019-02-10 18:44 ` Chris Murphy
2019-02-11 1:36 ` Qu Wenruo
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=b89f4970-c750-81d9-5eec-44a0ff14c4e1@gmail.com \
--to=arvidjaar@gmail.com \
--cc=jschoett@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