Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 354960 Details for
Bug 479544
sys-kernel/dracut-030 with <sys-fs/mdadm-3.2.6-r1 fails to boot with root on RAID because of missing option mdadm --offroot
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
mdadm.conf
mdadm.conf (text/plain), 2.74 KB, created by
Peter Volkov (RETIRED)
on 2013-08-02 17:45:44 UTC
(
hide
)
Description:
mdadm.conf
Filename:
MIME Type:
Creator:
Peter Volkov (RETIRED)
Created:
2013-08-02 17:45:44 UTC
Size:
2.74 KB
patch
obsolete
># mdadm configuration file ># ># mdadm will function properly without the use of a configuration file, ># but this file is useful for keeping track of arrays and member disks. ># In general, a mdadm.conf file is created, and updated, after arrays ># are created. This is the opposite behavior of /etc/raidtab which is ># created prior to array construction. ># ># ># the config file takes two types of lines: ># ># DEVICE lines specify a list of devices of where to look for ># potential member disks ># ># ARRAY lines specify information about how to identify arrays so ># so that they can be activated ># ># You can have more than one device line and use wild cards. The first ># example includes SCSI the first partition of SCSI disks /dev/sdb, ># /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second ># line looks for array slices on IDE disks. ># >#DEVICE /dev/sd[bcdjkl]1 >#DEVICE /dev/hda1 /dev/hdb1 ># ># If you mount devfs on /dev, then a suitable way to list all devices is: >#DEVICE /dev/discs/*/* ># ># ># The AUTO line can control which arrays get assembled by auto-assembly, ># meaing either "mdadm -As" when there are no 'ARRAY' lines in this file, ># or "mdadm --incremental" when the array found is not listed in this file. ># By default, all arrays that are found are assembled. ># If you want to ignore all DDF arrays (maybe they are managed by dmraid), ># and only assemble 1.x arrays if which are marked for 'this' homehost, ># but assemble all others, then use >#AUTO -ddf homehost -1.x +all ># ># ARRAY lines specify an array to assemble and a method of identification. ># Arrays can currently be identified by using a UUID, superblock minor number, ># or a listing of devices. ># ># super-minor is usually the minor number of the metadevice ># UUID is the Universally Unique Identifier for the array ># Each can be obtained using ># ># mdadm -D <md> ># >#ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371 >#ARRAY /dev/md1 super-minor=1 >#ARRAY /dev/md2 devices=/dev/hda1,/dev/hdb1 ># ># ARRAY lines can also specify a "spare-group" for each array. mdadm --monitor ># will then move a spare between arrays in a spare-group if one array has a failed ># drive but no spare >#ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df spare-group=group1 >#ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977 spare-group=group1 ># ># When used in --follow (aka --monitor) mode, mdadm needs a ># mail address and/or a program. This can be given with "mailaddr" ># and "program" lines to that monitoring can be started using ># mdadm --follow --scan & echo $! > /var/run/mdadm ># If the lines are not found, mdadm will exit quietly >#MAILADDR root@mydomain.tld >#PROGRAM /usr/sbin/handle-mdadm-events >DEVICE /dev/sd*[0-9] >ARRAY /dev/md/raid1 metadata=1.2 UUID=160643da:cfee732b:b7e74b81:d770b3dd name=sysresccd:raid1
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 479544
:
354952
|
354954
|
354956
| 354960 |
354962