From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Raid 1 recovery
Date: Thu, 19 Jan 2017 07:15:19 +0000 (UTC) [thread overview]
Message-ID: <pan$356c$39bebeff$a6d8a6ee$dcbb0048@cox.net> (raw)
In-Reply-To: CAJCQCtRYz9Gcqfc44Je9oqjXx-H-N8nbXp0TuzZcE6SN+ZCm8A@mail.gmail.com
Chris Murphy posted on Wed, 18 Jan 2017 14:30:28 -0700 as excerpted:
> On Wed, Jan 18, 2017 at 2:07 PM, Jon <jmoroney@hawaii.edu> wrote:
>> So, I had a raid 1 btrfs system setup on my laptop. Recently I upgraded
>> the drives and wanted to get my data back. I figured I could just plug
>> in one drive, but I found that the volume simply would not mount. I
>> tried the other drive alone and got the same thing. Plugging in both at
>> the same time and the volume mounted without issue.
>
> Requires mount option degraded.
>
> If this is a boot volume, this is difficult because the current udev
> rule prevents a mount attempt so long as all devices for a Btrfs volume
> aren't present.
OK, so I've known about this from the list for some time, but what is the
status with regard to udev/systemd (has a bug/issue been filed, results,
link?), and what are the alternatives, both for upstream, and for a dev,
either trying to be proactive, or currently facing a refusal to boot due
to the issue?
IOW, I run btrfs raid1 on /, setup before the udev rule I believe as it
worked back then, and I've known about the issue but haven't followed it
closely enough to know what I should do if faced with a dead device, or
what the current status is on alternatives to fix the problem longer
term, either locally (does simply disabling the rule work?) or upstream,
and what the alternatives might be along with the reasons this is still
shipping instead. And I'm asking in ordered to try to remedy that. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-01-19 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 21:07 Raid 1 recovery Jon
2017-01-18 21:30 ` Chris Murphy
2017-01-19 7:15 ` Duncan [this message]
2017-01-19 10:46 ` Andrei Borzenkov
2017-01-19 19:18 ` Chris Murphy
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='pan$356c$39bebeff$a6d8a6ee$dcbb0048@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).