On Tue, Jul 5, 2016 at 1:27 PM, Kai Krakow <hurikha...@gmail.com> wrote:
> Am Tue, 5 Jul 2016 12:53:02 -0600
> schrieb Chris Murphy <li...@colorremedies.com>:
>
>> For some reason I thought it was possible to do degraded Btrfs boots
>> by removing root=UUID= in favor of a remaining good block device, e.g.
>> root=/dev/vda2, and then adding degraded to rootflags. But this
>> doesn't work either on CentOS 7.2 or Fedora Rawhide. What happens is
>> systemd waits for vda2 (or by UUID) indefinitely, it doesn't even try
>> to mount the volume.
>>
>> I think it's due to the udev rule that's basically saying the device
>> isn't ready because not all of its devices are there.
>>
>> [root@f24m ~]# cat /usr/lib/udev/rules.d/64-btrfs.rules
>> # do not edit this file, it will be overwritten on update
>>
>> SUBSYSTEM!="block", GOTO="btrfs_end"
>> ACTION=="remove", GOTO="btrfs_end"
>> ENV{ID_FS_TYPE}!="btrfs", GOTO="btrfs_end"
>>
>> # let the kernel know about this btrfs filesystem, and check if it is
>> complete IMPORT{builtin}="btrfs ready $devnode"
>
> This doesn't come from the user-space tools but from the udev builtins,
> I think:
>
> # udevadm test-builtin btrfs[root@f24m ~]# udevadm test-builtin btrfs calling: test-builtin syspath missing # dnf provides /usr/lib/udev/rules.d/64-btrfs.rules Last metadata expiration check: 1:17:58 ago on Tue Jul 5 12:11:07 2016. systemd-udev-229-8.fc24.x86_64 : Rule-based device node and kernel event manager Repo : @System -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
