[Eisfair] [e1] eiskernel 2.8.0 (Status 'stable') verfügbar - 3.2er Kernel für eisfair-1

Thomas Bork tom at eisfair.org
Fr Feb 27 08:24:12 CET 2015


Am 27.02.2015 um 00:53 schrieb ich:

> Das hat bei ihm mit HOMEHOST zu tun. Das Raid wurde auf einem anderen
> Host erstellt und deswegen ist mdadm etwas zickig:

Dieser Bug ist dazu lesenswert:

https://bugzilla.redhat.com/show_bug.cgi?id=606481

mdadm-3.1.2 creates raid arrays using version 1.2 superblocks by 
default.  Version 1.2 superblocks will not automatically assemble with a 
numbered device name unless specifically told to do so.  There are two 
way to do this:

Pass the --name=<number> option to the mdadm --create command.  This 
will cause the name to be a simple number, and mdadm will assume that 
you want the array created with that number as the device name.  Aka, 0 
will get assembled as /dev/md0, 1 as /dev/md1, etc.

Create an ARRAY line in the mdadm.conf file that specifies the uuid of 
the array and the name you wish the array to have, eg.

ARRAY /dev/md0 uuid=<uuid>

For version 1.2 superblocks, the preferred way to create arrays is by 
using a name instead of a number.  For example, if the array is your 
home partition, then creating the array with the option --name=home will 
cause the array to be assembled with a random device number (which is 
what you are seeing now, when an array doesn't have an assigned number 
we start at 127 and count backwards), but there will be a symlink in 
/dev/md/ that points to whatever number was used to assemble the array. 
  The symlink in /dev/md/ will be whatever is in the name field of the 
superblock.  So in this example, you would have /dev/md/home that would 
point to /dev/md127 and the preferred method of use would be to access 
the device via the /dev/md/home entry.

A final note: mdadm will also check the homehost entry in the superblock 
and if it doesn't match either the system hostname or the HOSTNAME entry 
in mdadm.conf, then it will get assembled with a number postfix, so 
/dev/md/home might get assembled as /dev/md/home_0.  To turn this 
behavior off you either need to have a HOMEHOST entry in mdadm.conf that 
matches the homehost portion of the raid superblock or you need to have 
HOMEHOST <any> in the mdadm.conf file.

-- 
der tom
[eisfair-team]


Mehr Informationen über die Mailingliste Eisfair