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@xxxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
