[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
bin/55383: lvm is called before raidframe
>Synopsis: lvm is called before raidframe
>Arrival-Date: Sat Jun 13 06:05:00 +0000 2020
>Originator: The Grey Wolf
>Release: NetBSD 9.99.63
Star Wolf Innovations
System: NetBSD eddie.starwolf.com 9.99.63 NetBSD 9.99.63 (GENERIC) #1: Thu May 28 01:02:22 PDT 2020 greywolf%eddie.starwolf.com@localhost:/sys/arch/amd64/compile/GENERIC amd64
I have several raid volumes which do not autoconfigure for
whatever reason, so I need to start raidframe. Might have had
something to do with having higher-number raid volumes as sub-raids
of the lower number (raid2 == raid20 + raid21)? I don't know.
That, in and of itself, is an annoyance I will probably just have
to live with.
When my system restarted, the lvm rc script ran _before_ raidframe
did. I would expect that more people have LVM atop RAID than the
converse, so I patched /etc/rc.d/lvm to require raidframe before
attempting to configure the volume groups.
* set up a raid device (raid 1 + 0: 2 mirrored pairs, striped)
* set up config files for them in /etc. Set autoconfigure to 'yes'.
* Start slicing the RAID up into PVs, and allocate VGs and volumes.
* enable lvm and raidframe in /etc/rc.conf.
* reboot the machine.
* If your raid devices come up fine, well, this exercise is
pointless. I tried...(try again with autoconfigure to 'no').
* Notice that lvm runs before raidframe.
diff -u etc/rc.d/lvm.orig etc/rc.d/lvm
--- lvm.orig 2020-06-12 22:51:07.234896770 -0700
+++ lvm 2020-06-12 22:51:15.916870141 -0700
@@ -4,7 +4,7 @@
# PROVIDE: lvm
-# REQUIRE: root
+# REQUIRE: root raidframe
# BEFORE: DISKS
$_rc_subr_loaded . /etc/rc.subr
Main Index |
Thread Index |