From: Anand Jain <Anand.Jain@oracle.com>
To: "Vincent." <fensoft@gmail.com>
Cc: Suman Chakravartula <suman@rockstor.com>,
linux-btrfs@vger.kernel.org, linux-btrfs-owner@vger.kernel.org
Subject: Re: raid10 drive replacement
Date: Sat, 18 Oct 2014 12:37:53 +0800 [thread overview]
Message-ID: <5441EEA1.7080807@oracle.com> (raw)
In-Reply-To: <daf1096c58d3dd54392809f7d3f89e4d@sonic.net>
somethings aren't matching well. the issue is..
----
[ 6219.703606] Btrfs: too many missing devices, writeable mount is not
allowed
----
But per Vincent only xvdc is missing in a raid10 (both data and metadata
are raid10 ?)
Anand
On 10/18/14 10:02, Suman Chakravartula wrote:
>
> On 2014-10-17 18:47, Vincent. wrote:
>> Hi !
>>
>> I have a faulty drive in my raid10 and want it to be replaced.
>> Working drive are xvd[bef] and replacement drive is xvdc.
>>
> This is something I ran into the other day. Key difference is that I was
> running 3.17.1 kernel and 3.16 btrfs-progs
>
>> When I mount my drive in RW:
>> #mount -odegraded /dev/xvdb /tank
>> #dmesg -c
>> [ 6207.294513] btrfs: device fsid 728ef4d8-928c-435c-b707-f71c459e1520
>> devid 1 transid 551398 /dev/xvdb
>> [ 6207.327357] btrfs: allowing degraded mounts
>> [ 6207.477041] btrfs: bdev (null) errs: wr 15211054, rd 3038899, flush
>> 0, corrupt 0, gen 0
>> [ 6219.703606] Btrfs: too many missing devices, writeable mount is not
>> allowed
>> [ 6219.785929] btrfs: open_ctree failed
>>
>
> In my case, I was able to rw mount. May be update btrfs-progs and retry?
>
>> When I mount my drive in RO:
>> #mount -odegraded,ro /dev/xvdb /tank
>> #btrfs filesystem show
>> Label: none uuid: 728ef4d8-928c-435c-b707-f71c459e1520
>> Total devices 4 FS bytes used 4.70TiB
>> devid 1 size 2.73TiB used 2.73TiB path /dev/xvdb
>> devid 2 size 2.73TiB used 2.73TiB path
>> devid 3 size 2.73TiB used 2.73TiB path /dev/xvde
>> devid 4 size 2.73TiB used 2.73TiB path /dev/xvdf
>>
>> Btrfs v3.12
>>
>> Of course, because my mount is in RO, i can't add device and do a
>> balance:
>> #btrfs device add /dev/xvdc /tank
>> ERROR: error adding the device '/dev/xvdc' - Read-only file system
>>
>> Neither a "replace without disk":
>> #btrfs replace start -Br 2 /dev/xvdc /tank
>> ERROR: ioctl(DEV_REPLACE_START) failed on "/tank": Read-only file
>> system, no error
>>
> Because my mount was rw, replace worked.
>
>> FYI I'm on ubuntu 14.04 with btrfs 3.12
>>
>> Any idea ?
>> Thanks !
>> --
>> fensoft
>> --
>> 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
> --
> 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:[~2014-10-18 4:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 1:47 raid10 drive replacement Vincent.
2014-10-18 2:02 ` Suman Chakravartula
2014-10-18 4:37 ` Anand Jain [this message]
2014-10-18 23:12 ` Vincent.
2014-10-20 1:33 ` Anand Jain
2014-10-18 23:27 ` Duncan
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=5441EEA1.7080807@oracle.com \
--to=anand.jain@oracle.com \
--cc=fensoft@gmail.com \
--cc=linux-btrfs-owner@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=suman@rockstor.com \
/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