| 1 |
On Sat, May 17, 2014 at 8:56 AM, Stefan G. Weichinger <lists@×××××.at>wrote: |
| 2 |
|
| 3 |
> It seems to not detect or interpret correctly the fact that there are 2 |
| 4 |
> physical devices in there and then the "linux ..." line for grub.cfg |
| 5 |
> gets messed up, at least for me here. |
| 6 |
> |
| 7 |
|
| 8 |
ACK, genkernel initramfs doesn't "btrfs scan" and TSHTF. genkernel-next |
| 9 |
works though. But if you have it working now without any initramfs then |
| 10 |
obviously that is full of win (the LA kind, not the Redmond variety)! |
| 11 |
|
| 12 |
I am a bit mystified -- or perhaps ignorant -- as to how it came to be that |
| 13 |
btrfs has no option to automatically initiate a scan (like md raid does, |
| 14 |
when it's built into the kernel as a non-module). Surely people must want |
| 15 |
that feature. I can see how scanning the wrong partitions could lead to |
| 16 |
terrible mayhem, though, say, in a disaster recovery scenario where you |
| 17 |
binary-cloned a failing drive and forgot to take the old one out before |
| 18 |
booting or whatever.... but btrfs has the secret sauce to most likely |
| 19 |
figure stuff like that out auto-magically anyhow, using the genid... so |
| 20 |
what gives? Anyone know? |
| 21 |
|
| 22 |
Perhaps the option really is there and I simply never found it; admittedly |
| 23 |
I didn't look very hard -- regardless, I can't imagine the btrfs people |
| 24 |
just "never thought of it". If i's really not implemented, there must be a |
| 25 |
reason... and if that reason doesn't apply to my situation I might consider |
| 26 |
patching such a feature into my kernels as this is the only thing tying my |
| 27 |
workstation to an initramfs. |
| 28 |
|
| 29 |
-gmt |
Archives