From: Chris Murphy <lists@colorremedies.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: "Tomáš Hrdina" <thomas.rkh@gmail.com>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: Unable to mount degraded RAID5
Date: Mon, 4 Jul 2016 16:59:41 -0600 [thread overview]
Message-ID: <CAJCQCtRBQMZrAdY5zzbbgzvJ7VuK7BePmMKw_QzZBBeJsBjhAw@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtTPaxWBkmX=ADY7oh5bFjvODmuUNiGXtcBCfxw-c646LA@mail.gmail.com>
I just tried btrfs rescue chunk-recover (btrfs-progs 4.6) on new
Btrfs, 3x raid5 with 1 dev missing. I get:
[root@f24s ~]# btrfs rescue chunk-recover /dev/VG/2
Scanning: DONE in dev0, DONE in dev1
open with broken chunk error
Chunk tree recovery failed
So I don't think rescue chunk-recover can work degraded. At least,
it's not working now, and if it isn't meant to work it probably should
fail before it does the scanning, which takes a long time. I filed a
bug:
https://bugzilla.kernel.org/show_bug.cgi?id=121471
But in my case things still continue to work with btrfs-find-tree and
degraded mount works OK, so off hand I don't think the rescue
chunk-recover made things worse.
--
Chris Murphy
next prev parent reply other threads:[~2016-07-04 22:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 18:09 Unable to mount degraded RAID5 Tomáš Hrdina
2016-07-04 18:41 ` Chris Murphy
[not found] ` <95f58623-95a4-b5d2-fa3a-bfb957840a31@gmail.com>
2016-07-04 19:01 ` Chris Murphy
2016-07-04 19:11 ` Tomáš Hrdina
2016-07-04 20:43 ` Chris Murphy
2016-07-04 21:10 ` Tomáš Hrdina
2016-07-04 22:42 ` Chris Murphy
2016-07-04 22:59 ` Chris Murphy [this message]
2016-07-05 7:12 ` Tomáš Hrdina
2016-07-05 3:48 ` Andrei Borzenkov
2016-07-05 15:13 ` Chris Murphy
2016-07-05 18:40 ` Tomáš Hrdina
2016-07-05 23:19 ` Chris Murphy
2016-07-06 8:07 ` Tomáš Hrdina
2016-07-06 16:08 ` Chris Murphy
2016-07-06 17:50 ` Tomáš Hrdina
2016-07-06 18:12 ` Chris Murphy
2016-07-09 17:30 ` Tomáš Hrdina
2016-07-09 18:33 ` Chris Murphy
2016-07-10 7:01 ` Tomáš Hrdina
2016-07-10 20:08 ` Chris Murphy
2016-07-11 17:17 ` Tomáš Hrdina
2016-07-11 19:25 ` Chris Murphy
[not found] <CAFDLS-CtnVDtD8d=Wtp0tVokKJ6pjptpX7MR862dThBJvSPC5g@mail.gmail.com>
2016-07-06 17:12 ` Fwd: " Gonzalo Gomez-Arrue Azpiazu
2016-07-06 18:19 ` Chris Murphy
2016-07-07 12:24 ` Gonzalo Gomez-Arrue Azpiazu
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=CAJCQCtRBQMZrAdY5zzbbgzvJ7VuK7BePmMKw_QzZBBeJsBjhAw@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=thomas.rkh@gmail.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;
as well as URLs for NNTP newsgroup(s).