linux-kernel - [PROBMEL] MD doesn't like /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 for Android: free password hash cracker in your pocket

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

Message-ID: <8d158e1f0702260055m5d3cf93cqce58e366d677c090@mail.gmail.com>
Date:	Mon, 26 Feb 2007 09:55:54 +0100
From:	"Patrick Ale" <patrick.ale@...il.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: [PROBMEL] MD doesn't like /dev/disk/by-id

Hi,

I posted this a while ago aswell :)

MD can't start anymore when /etc/mdadm.conf uses /dev/disk/by-id/* ,
it bluntly tells you there are no suiteable drives.

Since libata tends to mangle my drive order by every reboot since I
use 3 controllers and the drivers dont generate uevents always in the
same sequence the only thing left to use are UUIDs.

Now, this isnt a problem but is this the *only* way the mdadm devices
will startable now and is this the only way the MD module will
support?

And if yes, maybe this should be communicated somewhere, cause
something tells me I am not the only one who had this problem or will
have :)

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/