re: RAIDframe raidN device order

[matthew green <mrg%eterna.com.au@localhost>]

Edgar Fu? writes:
> When I configure my RAIDframe devcices using raidN.conf, I may run into the 
> problem that after a reboot, the MPT controller may have assigned new pseudo 
> SCSI Target ID to my SAS discs, so they get different sdN numbers and the 
> array may fail to configure.
> The solution seems to be to use auto-configuration for the arrays. But then, 
> how do I know which raidN device is which array?
> Is there any way to use UUIDs to solve the problem?
> 

as David said, the same raidN will be persisted across reboots as long
as there are no clashes (there is no stable algo for this, unfortunatley.)

however, it is possible to mount via UUID as well.  this may require
using gpt -- i've only used it on large disks so far that require gpt.

eg, i have this:

raid1: RAID Level 1
raid1: Components: /dev/dk4 /dev/dk1
raid1: Total Sectors: 5860532864 (2861588 MB)
raid1: GPT GUID: 1cc29189-34eb-11e0-92d8-0018f34ccff6
dk7 at raid1: 1cc291b3-34eb-11e0-92d8-0018f34ccff6

and i could mount "dk7" via /dev/dk7, but i use this in my fstab:

NAME=1cc291b3-34eb-11e0-92d8-0018f34ccff6  /stuff  ffs  ro  1 3

so it shouldn't matter what happens to the underlying storage as long
as the gpt remains.


.mrg.