1 |
On Thu, May 28, 2015 at 1:03 PM, Peter Humphrey <peter@××××××××××××.uk> wrote: |
2 |
> On Thursday 28 May 2015 15:36:04 I wrote: |
3 |
>> On Thursday 28 May 2015 08:44:27 Rich Freeman wrote: |
4 |
>> > With an approach like yours, mdadm will attempt to create md1 by |
5 |
>> > looking ONLY at sda1 and sdb1, and if that pair forms a valid array it |
6 |
>> > is started, and if not it is not. If you add a new drive to your |
7 |
>> > system or for whatever reason the kernel/udev rules change a little or |
8 |
>> > some race condition changes a little then your devices might get |
9 |
>> > different names, and the array will not be assembled. |
10 |
>> |
11 |
>> Hmm. I wonder if that's what's happening to me. Perhaps I'd better adopt |
12 |
>> UUIDs then, once I work out what mine are. Thanks for the advice. |
13 |
> |
14 |
> I've found blkid, which tells me the UUIDs of my various devices, thus: |
15 |
> |
16 |
> # blkid /dev/md7 |
17 |
> /dev/md7: UUID="ycGMf9-hEP2-tjT4-AtkJ-n8RI-pZ44-RqvlEY" |
18 |
> TYPE="LVM2_member" |
19 |
|
20 |
Just keep in mind that the UUID that goes into mdadm.conf might not be |
21 |
the same UUID returned by blkid. I'm honestly not certain either way. |
22 |
You can get the mdadm ID from mdadm --detail --scan. |
23 |
|
24 |
> |
25 |
> Two odd things: |
26 |
> 1. /dev/md7 is the physical volume in which logical volumes are defined, |
27 |
> so I'm surprised to see TYPE="LVM2_member". |
28 |
|
29 |
I'm pretty sure this is fine. It recognizes it as an LVM pv, so that |
30 |
makes it an LVM2 member. |
31 |
|
32 |
> 2. There is no entry corresponding to /dev/md7 under /dev/disk/by-uuid, |
33 |
> though /dev/md1 and /dev/md5 do have entries there [1]. |
34 |
|
35 |
udev may be configured to not create uuid symlinks for LVM pvs (since |
36 |
you wouldn't directly mount them anyway). The others contain |
37 |
filesystems and do get symlinks. |
38 |
|
39 |
|
40 |
> |
41 |
> What should I be doing about this? |
42 |
|
43 |
I'd probably just edit your mdadm.conf to be more liberal with |
44 |
scanning, and add the arrays output by mdadm --detail --scan to your |
45 |
config file. That alone may make your problems go away, and it should |
46 |
be pretty harmless. |
47 |
|
48 |
> |
49 |
> I assume that the ../../dm-N links refer to the LVs - there are 15 of them. |
50 |
> md7 is conspicuous by its absence. This seems like a problem to me, and it |
51 |
> may account for /dev/md7 sometimes not being started at boot time. |
52 |
> |
53 |
|
54 |
LVM is just a wrapper around DM, so that is normal. Nothing about |
55 |
what you've written here concerns me. |
56 |
|
57 |
-- |
58 |
Rich |