From: Andy Smith <andy@strugglers.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Problems with "btrfs dev remove" of dead disk
Date: Mon, 15 Feb 2016 00:13:56 +0000 [thread overview]
Message-ID: <20160215001356.GR4290@bitfolk.com> (raw)
In-Reply-To: <CAJCQCtSTWLXWCwNVmcWc6zt+fGAv-pJy73VtL0xTnyaw10MTrw@mail.gmail.com>
Hi Chris,
On Sun, Feb 14, 2016 at 04:49:29PM -0700, Chris Murphy wrote:
> On Sun, Feb 14, 2016 at 2:55 PM, Andy Smith <andy@strugglers.net> wrote:
> > $ sudo btrfs dev remove /dev/sdh /srv/tank
> > ERROR: not a block device: /dev/sdh
>
>
> Since now it's a missing device, it should be
>
> sudo btrfs device remove missing /srv/tank
$ sudo btrfs device remove missing /srv/tank
ERROR: error removing device 'missing': no missing devices found to remove
> But I'm not sure if this works when the volume is not already mounted
> degraded.
I have now done:
# mount -oremount,degraded /srv/tank
and tried again, but it produces the same response ("mount" now does
show "degraded" as one of the mount flags, however).
I have not yet tried completely unmounting it and mounting it again.
> it really doesn't make sense to me you'd want to increase risk of
> more Btrfs problems when such known things are now fixed. Consider
> 4.1.15 if you want a stable long term yet currently supportable
> kernel.
It is inconvenient to reboot just now, so if I'm able to fix things
without doing so (e.g. by balance or replace) then I would like to.
If that won't be possible then I will of course boot into a newer
kernel at the same time.
If I end up booting into 4.1.15 then it should be possible to mount
degraded and remove missing?
Cheers,
Andy
next prev parent reply other threads:[~2016-02-15 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 21:55 Problems with "btrfs dev remove" of dead disk Andy Smith
2016-02-14 23:49 ` Chris Murphy
2016-02-15 0:13 ` Andy Smith [this message]
2016-02-15 3:40 ` Anand Jain
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=20160215001356.GR4290@bitfolk.com \
--to=andy@strugglers.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.