linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Bodenbinder <matthias@bodenbinder.de>
To: linux-btrfs@vger.kernel.org
Subject: Question: raid1 behaviour on failure
Date: Mon, 18 Apr 2016 07:06:27 +0200	[thread overview]
Message-ID: <nf1q0j$ug4$1@ger.gmane.org> (raw)

Hi,

I have a raid1 with 3 drives: 698, 465 and 232 GB. I copied 1,7 GB data to that raid1, balanced the filesystem and then removed the bigger drive (hotplug). 

The data was still available. Now I copied the /root directory to the raid1. It showed up via ls -l. Then I plugged in the missing hard drive again (hotplug). After a few seconds "btrfs fi show" is giving output as usual:

Label: none  uuid: 16d5891f-5d52-4b29-8591-588ddf11e73d
	Total devices 3 FS bytes used 1.60GiB
	devid    1 size 698.64GiB used 4.03GiB path /dev/sdg
	devid    2 size 465.76GiB used 4.03GiB path /dev/sdh
	devid    3 size 232.88GiB used 0.00B path /dev/sdi

The /root is still showing up, but the raid1 is now mounted in *read-only* mode. 

I umounted it and mounted it again. Now the /root directory on the raid1 is no longer available. Its gone.

I guess I missed some important step to recover the degraded raid1 before umounting it.

What is it that I missed?

Matthias


             reply	other threads:[~2016-04-18  5:30 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18  5:06 Matthias Bodenbinder [this message]
2016-04-18  7:22 ` Question: raid1 behaviour on failure Qu Wenruo
2016-04-20  5:17   ` Matthias Bodenbinder
2016-04-20  7:25     ` Qu Wenruo
2016-04-21  5:22       ` Matthias Bodenbinder
2016-04-21  5:43         ` Qu Wenruo
2016-04-21  6:02           ` Liu Bo
2016-04-21  6:09             ` Qu Wenruo
2016-04-21 17:40           ` Matthias Bodenbinder
2016-04-22  6:02             ` Qu Wenruo
2016-04-23  7:07               ` Matthias Bodenbinder
2016-04-23  7:17                 ` Matthias Bodenbinder
2016-04-26  8:17                 ` Satoru Takeuchi
2016-04-26 15:16                 ` Henk Slager
2016-04-20 13:32     ` Anand Jain
2016-04-21  5:15       ` Matthias Bodenbinder
2016-04-21  7:19         ` Anand Jain
2016-04-21  6:23     ` Satoru Takeuchi
2016-04-21 11:09       ` Austin S. Hemmelgarn
2016-04-21 11:28       ` Henk Slager
2016-04-21 17:27         ` Matthias Bodenbinder
2016-04-26 16:19           ` Henk Slager
2016-04-26 16:42             ` Holger Hoffstätte
2016-04-28  5:12               ` Matthias Bodenbinder
2016-04-28  5:24                 ` Gareth Pye
2016-04-28  8:08                   ` Duncan
2016-04-28  5:09             ` Matthias Bodenbinder
2016-04-28 19:14               ` Henk Slager
     [not found]       ` <57188534.1070408@jp.fujitsu.com>
2016-04-21 11:58         ` Qu Wenruo
2016-04-22  2:21           ` Satoru Takeuchi
2016-04-22  5:32             ` Qu Wenruo
2016-04-22  6:17               ` Satoru Takeuchi

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='nf1q0j$ug4$1@ger.gmane.org' \
    --to=matthias@bodenbinder.de \
    --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).