From: Michael Welsh Duggan <mwd@md5i.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Fixing a degraded RAID
Date: Fri, 18 Apr 2014 23:23:56 -0400 [thread overview]
Message-ID: <87ppkeato3.fsf@maru2.md5i.com> (raw)
In-Reply-To: 87y4z2avvz.fsf@maru2.md5i.com
Michael Welsh Duggan <mwd@md5i.com> writes:
> I had a disk in my RAID0 die:
My mistake. This was a stupid typo. The drives were in a RAID 1
configuration. Both data and metadata are DUP'd.
root@maru2:~# /usr/local/src/btrfs-progs/btrfs fi df /mnt/
Data, RAID1: total=353.00GiB, used=328.24GiB
System, single: total=32.00MiB, used=56.00KiB
Metadata, RAID1: total=4.00GiB, used=1.43GiB
> root@maru2:~# /usr/local/src/btrfs-progs/btrfs fi show 8c530f6f-7592-4d57-854d-1fae33ae7cb6
> Label: none uuid: 8c530f6f-7592-4d57-854d-1fae33ae7cb6
> Total devices 3 FS bytes used 329.66GiB
> devid 1 size 1.79TiB used 357.03GiB path /dev/sdd1
> devid 3 size 931.51GiB used 178.00GiB path /dev/sdf
> *** Some devices missing
>
> Btrfs v3.12-43-gc2081e2-dirty
>
> So, I try to mount it with -o degraded. That fails, implying that a
> degraded mount needs to be read-only. So I successfully mount it read
> only. Then I want to add a new disk to replace the missing one:
>
> root@maru2:~# /usr/local/src/btrfs-progs/btrfs dev add /dev/sdg /mnt/
> ERROR: error adding the device '/dev/sdg' - Read-only file system
>
> So I can't add a disk if it's mounted read-only, and can't mount it
> read-write? What am I missing? What's my way around this?
--
Michael Welsh Duggan
(md5i@md5i.com)
next prev parent reply other threads:[~2014-04-19 3:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 2:36 Fixing a degraded RAID Michael Welsh Duggan
2014-04-19 2:49 ` Chris Murphy
2014-04-19 2:58 ` Michael Welsh Duggan
2014-04-19 3:23 ` Michael Welsh Duggan [this message]
2014-04-19 4:54 ` Chris Murphy
2014-04-19 11:23 ` Xavier Bassery
2014-04-19 15:31 ` Michael Welsh Duggan
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=87ppkeato3.fsf@maru2.md5i.com \
--to=mwd@md5i.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