| 1 |
On Saturday 03 May 2014 20:40:47 J. Roeleveld wrote: |
| 2 |
> On Saturday, May 03, 2014 06:09:21 PM Peter Humphrey wrote: |
| 3 |
> > Hope I'm not butting in here, but... |
| 4 |
> > |
| 5 |
> > Although I don't run systemd nor do I have an initramfs, the grub.conf |
| 6 |
> > entry for my LVM2 setup is just these two lines: |
| 7 |
> > |
| 8 |
> > title=Gentoo Linux 3.12.13 |
| 9 |
> > kernel /boot/kernel-x86_64-3.12.13-gentoo root=/dev/md5 |
| 10 |
> > net.ifnames=0 |
| 11 |
> |
| 12 |
> That works with metadata=0.9 when creating the raid-1 device and not having |
| 13 |
> " / " on LVM. |
| 14 |
|
| 15 |
Yes, I should have added that I have /boot on straight ext2 on /dev/sda1 (sdb1 |
| 16 |
is ready in case I decide to raid it). The file-system root is on raid1 and |
| 17 |
everything else is in LVs on /dev/md7, also raid1. I did it that way to keep |
| 18 |
booting simple. And I've used 0.9 metadata throughout. |
| 19 |
|
| 20 |
> I only have /boot on a raid-1 with metadata=0.9. |
| 21 |
> All the other partitions are LVs with the lvm layer ontop of a raid-0. |
| 22 |
> (no important data is stored locally on the desktop machines) |
| 23 |
|
| 24 |
I wanted the little extra safety of raid1 because this is where I keep all my |
| 25 |
data. |
| 26 |
|
| 27 |
> > I've noticed several times (often much to my annoyance before I discovered |
| 28 |
> > what to do about it*) that starting of the raid arrays is automatic, |
| 29 |
> > apparently done by the kernel though I could be wrong about that. In fact |
| 30 |
> > I was astonished to find not long ago that I'd been running for a year or |
| 31 |
> > two with neither lvm2 nor mdraid installed! |
| 32 |
> |
| 33 |
> Something must have handled the LVM part. Afaik, there is no kernel auto- |
| 34 |
> detect for LVM. |
| 35 |
|
| 36 |
Yes, that's why I mentioned it. If it's not the kernel I don't know what else |
| 37 |
it could have been. Udev? I don't see anything relevant under /etc/udev. |
| 38 |
|
| 39 |
> > * SystemRescueCD and the Gentoo minimal installation CD both start any |
| 40 |
> > raid |
| 41 |
> > arrays they find and apply their own names to them. It is then impossible, |
| 42 |
> > or so I thought, to resume an interrupted installation process. Of course, |
| 43 |
> > all I had to do was "mdadm --stop /dev/md127" etc. |
| 44 |
> |
| 45 |
> Yes, I noticed that annoyance myself. I would much prefer it to default to |
| 46 |
> more logical names. |
| 47 |
|
| 48 |
If the docs had included that little snippet I'd have saved myself many a |
| 49 |
frustrating hour. I'll only look stupid if I tell you how many ;-) |
| 50 |
|
| 51 |
Anyway, I don't want to hijack the thread. I just wanted to point out that |
| 52 |
raid arrays don't need lvm2 or mdraid present to auto-start, at least not on |
| 53 |
my openrc box which also has no initramfs. |
| 54 |
|
| 55 |
-- |
| 56 |
Regards |
| 57 |
Peter |
Archives