From: Anand Jain <anand.jain@oracle.com>
To: Martin <develop@imagmbh.de>, linux-btrfs@vger.kernel.org
Subject: Re: rw-mount-problem after raid1-failure
Date: Wed, 10 Jun 2015 09:19:37 +0800 [thread overview]
Message-ID: <557790A9.3080705@oracle.com> (raw)
In-Reply-To: <2227931.EqpnWnc32X@malu-aspire-v3-771>
On 06/09/2015 01:10 AM, Martin wrote:
> Hello!
>
> I have a raid1-btrfs-system (Kernel 3.19.0-18-generic, Ubuntu Vivid Vervet,
> btrfs-tools 3.17-1.1). One disk failed some days ago. I could remount the
> remaining one with "-o degraded". After one day and some write-operations
> (with no errrors) I had to reboot the system. And now I can not mount "rw"
> anymore, only "-o degraded,ro" is possible.
>
> In the kernel log I found BTRFS: too many missing devices, writeable mount is
> not allowed.
>
> I read about https://bugzilla.kernel.org/show_bug.cgi?id=60594 but I did no
> conversion to a single drive.
>
> How can I mount the disk "rw" to remove the "missing" drive and add a new one?
> Because there are many snapshots of the filesystem, copying the system would
> be only the last alternative ;-)
How many disks you had in the RAID1. How many are failed ?
Thanks Anand
> Thanks
>
> Martin
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-06-10 1:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 17:10 rw-mount-problem after raid1-failure Martin
2015-06-10 1:19 ` Anand Jain [this message]
2015-06-10 3:58 ` Duncan
2015-06-10 6:38 ` Anand Jain
2015-06-10 6:58 ` Martin
2015-06-10 7:46 ` Anand Jain
2015-06-10 12:05 ` Martin
2015-06-11 0:04 ` Anand Jain
2015-06-11 13:03 ` Martin
2015-06-12 10:38 ` Anand Jain
2015-06-14 18:24 ` Martin
2015-06-15 0:58 ` 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=557790A9.3080705@oracle.com \
--to=anand.jain@oracle.com \
--cc=develop@imagmbh.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