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 <a...@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
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
