On Mon, Jan 31, 2011 at 03:03:58PM +0100, martin f krafft wrote: > also sprach Mario 'BitKoenig' Holbe <mario.ho...@tu-ilmenau.de> > [2011.01.26.2235 +0100]: > > On a system without lvm or cryptsetup installed mdadm-raid stop gets > > scheduled quite early: > > ... particularly before umountfs. > > > > I'd suggest altering mdadm-raid's Stop-Dependencies similar to lvm2 > > and/or cryptdisks-early. > How? Can you please provide a concrete and tested solution?
The attached patch schedules mdadm-raid the same with or without
cryptsetup or lvm2 installed. It's tested.
One could probably even think about X-Stop-After: umountroot, but I'm
not sure about the side-effects.
regards
Mario
--
We know that communication is a problem, but the company is not going to
discuss it with the employees.
-- Switching supervisor, AT&T Long Lines Division
--- /etc/init.d/mdadm-raid.orig 2010-09-03 10:44:09.000000000 +0200 +++ /etc/init.d/mdadm-raid 2011-01-31 15:22:50.000000000 +0100 @@ -10,8 +10,10 @@ # Provides: mdadm-raid # Required-Start: mountkernfs # Should-Start: udev devfsd +# X-Start-Before: checkfs mountall # Required-Stop: mountkernfs # Should-Stop: udev devfsd +# X-Stop-After: umountfs # Default-Start: S # Default-Stop: 0 6 # Short-Description: MD array assembly
signature.asc
Description: Digital signature
