From: Ian Kumlien <ian.kumlien@gmail.com>
To: Hugo Mills <hugo@carfax.org.uk>,
Ian Kumlien <ian.kumlien@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [btrfs tools] ability to fail a device...
Date: Tue, 8 Sep 2015 22:00:57 +0200 [thread overview]
Message-ID: <CAA85sZtUJCDQ2=7KNFapZXPXb8SseiLCBvJVBDkoUa_7Ah8idQ@mail.gmail.com> (raw)
In-Reply-To: <CAA85sZvJdOyUhZqFy4bWEPbKfM7k9gKU4vui9k+rRDmnWvPSxQ@mail.gmail.com>
On 8 September 2015 at 21:55, Ian Kumlien <ian.kumlien@gmail.com> wrote:
> On 8 September 2015 at 21:43, Ian Kumlien <ian.kumlien@gmail.com> wrote:
>> On 8 September 2015 at 21:34, Hugo Mills <hugo@carfax.org.uk> wrote:
>>> On Tue, Sep 08, 2015 at 09:18:05PM +0200, Ian Kumlien wrote:
> [--8<--]
>
>>> Physically removing it is the way to go (or disabling it using echo
>>> offline >/sys/block/sda/device/state). Once you've done that, you can
>>> mount the degraded FS with -odegraded, then either add a new device
>>> and balance to restore the RAID-1, or balance with
>>> -{d,m}convert=single to drop the redundancy to single.
>>
>> This did not work...
>
> And removing the pyscial device is not the answer either... until i
> did a read only mount ;)
>
> Didn't expect it to fail with unable to open ctree like that...
Someone thought they were done too early, only one disk => read only
mount. But, readonly mount => no balance.
I think something is wrong....
btrfs balance start -dconvert=single -mconvert=single /mnt/disk/
ERROR: error during balancing '/mnt/disk/' - Read-only file system
btrfs dev delete missing /mnt/disk/
ERROR: error removing the device 'missing' - Read-only file system
Any mount without ro becomes:
[ 507.236652] BTRFS info (device sda2): allowing degraded mounts
[ 507.236655] BTRFS info (device sda2): disk space caching is enabled
[ 507.325365] BTRFS: bdev (null) errs: wr 2036894, rd 2031380, flush
705, corrupt 0, gen 0
[ 510.983321] BTRFS: too many missing devices, writeable mount is not allowed
[ 511.006241] BTRFS: open_ctree failed
And one of them has to give! ;)
> [--8<--]
next prev parent reply other threads:[~2015-09-08 20:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 19:18 [btrfs tools] ability to fail a device Ian Kumlien
2015-09-08 19:34 ` Hugo Mills
2015-09-08 19:43 ` Ian Kumlien
2015-09-08 19:55 ` Ian Kumlien
2015-09-08 20:00 ` Ian Kumlien [this message]
2015-09-08 20:08 ` Chris Murphy
2015-09-08 20:13 ` Ian Kumlien
2015-09-08 20:17 ` Chris Murphy
2015-09-08 20:24 ` Ian Kumlien
2015-09-08 20:28 ` Hugo Mills
2015-09-08 20:33 ` Ian Kumlien
2015-09-08 20:40 ` Hugo Mills
2015-09-09 1:35 ` Anand Jain
2015-09-09 7:07 ` Ian Kumlien
2015-09-09 8:54 ` Ian Kumlien
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='CAA85sZtUJCDQ2=7KNFapZXPXb8SseiLCBvJVBDkoUa_7Ah8idQ@mail.gmail.com' \
--to=ian.kumlien@gmail.com \
--cc=hugo@carfax.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).