Skip to Content.
Sympa Menu

sm-grimoire-bugs - [SM-Grimoire-Bugs] [Bug 13450] init.d mountroot.sh and raid

sm-grimoire-bugs AT lists.ibiblio.org

Subject: SourceMage Grimoire Bug List

List archive

Chronological Thread  
  • From: bugzilla-daemon AT bugs.sourcemage.org
  • To: sm-grimoire-bugs AT lists.ibiblio.org
  • Subject: [SM-Grimoire-Bugs] [Bug 13450] init.d mountroot.sh and raid
  • Date: 31 May 2011 10:52:55 -0000

http://bugs.sourcemage.org/show_bug.cgi?id=13450


Arjan Bouter <abouter AT sourcemage.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |abouter AT sourcemage.org
AssignedTo|sm-grimoire-bugs AT lists.ibib |abouter AT sourcemage.org
|lio.org |




--- Comment #5 from Arjan Bouter <abouter AT sourcemage.org> 2011-05-31
05:52:52 ---
I'll see what I can do while tinkering with IMP.

But we do need to discuss what we expect from init scripts.

In LVM's case, the root filesystem needs to be handled in an initramfs if it's
on LVM, as there is no way for it to auto-start that I'm aware of. Once / is
mounted, scanning for other volumes and mounting them is trivial.

For software-raid the array's are auto-started when the partitions are marked
properly, the array is created with the right options and the kernel has
CONFIG_MD_AUTODETECT enabled right?
(it has been quite a while since I've used sw-raid.)
So shouldn't this be handled by normal filesystem mounting? Mdadm running as a
daemon to keep track of the arrays should then move to runlevel 3 so it can
actually send the warnings.

I'll need some pointers on how to enable encrypted filesystems if we want
those
properly supported.

--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



  • [SM-Grimoire-Bugs] [Bug 13450] init.d mountroot.sh and raid, bugzilla-daemon, 05/31/2011

Archive powered by MHonArc 2.6.24.

Top of Page