Roger Price composed on 2024-11-26 03:57 (UTC-0500):
> Felix Miata wrote:
>> Members of a raid filesystem have to be seen as an integral part of one
>> filesystem,
>> a special case. It's another reason I stick to use of LABELs.
>> # lsblk -f | egrep -A1 'raid|NAME'
>> NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE%
>> MOUNTPOINTS
>> --
>> ├─sda5 linux_raid_member 1.0 msi85:0tmp 6cb3…
>> │ └─md0 ext4 1.0 hr18md0tmp 8aea…
>> --
>> ├─sdb5 linux_raid_member 1.0 msi85:0tmp 6cb3…
>> │ └─md0 ext4 1.0 hr18md0tmp 8aea…
> It makes sense to me that md0 should be reported twice with the same UUID,
> but
> surely the underlying hardware should be getting a unique UUID?
Answered well upthread by others.
> The use of LABELs is attractive, but I notice you have the same label for
> sda5
> and sdb5. This means you cannot intervene on "msi85:0tmp". You have to
> specify
> sda5 or sdb5.
Not at all. hr18md0tmp is an ext4 filesystem LABEL. I wouldn't want to disturb
its
two underlying partitions separately except via mdadm.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
