On Tue, Jan 18, 2011 at 01:35:59PM +0100, Mario 'BitKoenig' Holbe wrote: > with the new Dependency based boot sequence the boot sequencing of > mdadm's mdadm-raid ad initscripts's hostname.sh changed.
Hmmm, I guess since this bug is still open I don't need to create a new
one :)
I found another issue with mdadm-raid, Dependency based boot sequence,
and stop levels (rc0, rc6) this time:
mdadm-raid's Stop-Dependencies are not sufficient to schedule it late in
the stop sequence.
On a system with lvm or cryptsetup installed this does not attract
attention because lvm's or cryptsetup's Stop-Dependencies schedule
mdadm-raid late enough:
...
K08umountfs
K09cryptdisks
K10lvm2
K11cryptdisks-early
K12mdadm-raid
K12umountroot
K14halt
On a system without lvm or cryptsetup installed mdadm-raid stop gets
scheduled quite early:
K03mdadm-raid
K04sysklogd
K05hwclock.sh
K05sendsigs
K06umountnfs.sh
K07networking
K08umountfs
K09umountroot
K10halt
... particularly before umountfs.
I'd suggest altering mdadm-raid's Stop-Dependencies similar to lvm2
and/or cryptdisks-early.
regards
Mario
--
File names are infinite in length where infinity is set to 255 characters.
-- Peter Collinson, "The Unix File System"
signature.asc
Description: Digital signature
