[ale] OS or Hardware issue?

Jim Kinney jim.kinney at gmail.com
Tue Apr 20 15:42:19 EDT 2021

UUID is the solution. It's just hard to read.

On April 20, 2021 2:32:30 PM EDT, Phil Turmel via Ale <ale at ale.org> wrote:
>Well, it has been this way for several years.  Good luck getting it 
>classified as a bug.
>Using dynamically allocated names in fstab (and similar) is the bug. 
>is only "simpler" until it breaks your setup.
>On 4/20/21 9:23 AM, Leam Hall via Ale wrote:
>> I'm quite in the opposite camp. Using devices simplifies support for
>> base OS. Using LVM is nice when things might move, and you know
>> have a fully operational OS and LVM suite going.
>> If a kernel changes the device order, that really seems like a bug.
>> On 4/20/21 8:58 AM, Phil Turmel via Ale wrote:
>>> Under no circumstances should you ever place first-level block
>>> names into your config files (like fstab).  Though not likely, any 
>>> kernel update can change the order.  And in some cases, kernel 
>>> parallelism can mix the sequence from multiple PCI devices.  (Also 
>> not
>>> likely, but I've seen it.)  Use a LABEL or UUID instead of
>>> Names based on LVM group and volume names are fine.
>Ale mailing list
>Ale at ale.org
>See JOBS, ANNOUNCE and SCHOOLS lists at

Computers amplify human error
Super computers are really cool
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.ale.org/pipermail/ale/attachments/20210420/7ce495d2/attachment.htm>

More information about the Ale mailing list