guido_kuenne posted on Sat, 03 Oct 2015 22:53:46 +0200 as excerpted: > Beginner here, so just if it helps: My two-device raid 1 mounts on boot > in Fedora 22 (uuid in fstab, no further devices specified) but I mount > the fs via uuid while Sjoerd mounted subvolumes. From what I understand > (not much) it's either an subvolume issue or Fedora must then somehow > perform a device scan before handling fstab. I'm guessing fedora has btrfs device scan in its initr*. I believe dracut is a fedora based project and what they use to generate their initr*s. I too use dracut for my initr* generation, and btrfs is an optional module which I obviously load (in a site-specific custom initr* here, on gentoo), and I know it has the btrfs device scan in the initr* here, so presumably it's in the general purpose initr* they use as well. The only way it wouldn't would be if they didn't include the btrfs dracut module at all in their initr*, and I think btrfs is popular enough that they include it, so... ... So even if Fedora doesn't include btrfs device scan in the real-root init (which I'd guess it does as well), it's going to be in the initr*, which means unless the devices for that btrfs aren't plugged in until after boot, it should see them due to the scan at the initr* stage, and "just work", mounting the btrfs without problems at any time after 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
