linux-kernel - Re: [PROBLEM] Can't start MD devices by using /dev/disk/by-id

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <8d158e1f0702132328u104c89d4r3154b87c2b5f6e5c@mail.gmail.com>
Date:	Wed, 14 Feb 2007 08:28:25 +0100
From:	"Patrick Ale" <patrick.ale@...il.com>
To:	"Bill Davidsen" <davidsen@....com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PROBLEM] Can't start MD devices by using /dev/disk/by-id

> >
> Just out of curiosity, why did you do this in such a manual way instead
> of just using the UUID? I would think every time you replace a failed
> drive you would have to go edit the files all over again.

Oh, there is a very simple reason for that.
These md arrays exist for a year of three allready, from the time I
used raidtool instead of mdadm.

So when I switched to to mdadm, I just got the /etc/raidtab file and
migrated it to /etc/mdadm.conf, since /etc/raidtab worked with
blockdevices and not UIDs (correct me if I am wrong and overlooked
this featute), the mdadm.conf ended up with these devices too.

Next to that, there is a, for me at least, practicle reason. I keep
adding harddisks, and when I use the block devices rather than UIDS,
and I get problems like yesterday, I have the blockdevice or serial
number of the disk, which makes it easier to look in my case where the
potential problem might be. If I work with UIDs and something goes
wrong when doing an mdadm --assemble, then I'll first have to look up
which disks belong to which UID, which costs time.

OR! which is also very possible, maybe there is a way easier way to
pinpoint which drives belong to which array before starting the array,
which I don't know about yet. So please, if you have suggestions, let
me know :)

Take care!

Patrick
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/