Summary: | sys-kernel/genkernel needs to be updated to work with the new btrfs-progs | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Austin S. Hemmelgarn <ahferroin7> |
Component: | genkernel | Assignee: | Gentoo Genkernel Maintainers <genkernel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ahferroin7, bugs, martin.dummer |
Priority: | Normal | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | correct btrfs program name |
Description
Austin S. Hemmelgarn
2014-01-30 01:45:58 UTC
Created attachment 373788 [details, diff]
correct btrfs program name
Same problem. I've got a system with a RAID 1 btrfs root partition. Using the attached patch & its working fine.
Using a lot of rootflags=device= goop works, but it would be nice to do this the proper way with btrfs device scan. Just for reference to anyone who may be interested, I've switched to sys-kernel/genkernel-next as that does actually handle current btrfs-progs correctly (although you need to add BTRFS=1 to /etc/genkernel.conf for it to actually include btrfs support in the generated initramfs). This should be fixed in HEAD. The fix will be in v3.4.53. I am leaving this open until v3.4.53 is tagged to make it easier to track it. Already released |