hptrr disk labeling

[Ronald Klop]

On Sun, 03 Jun 2012 06:19:38 +0200, Randy Bush <randy at psg.com> wrote:

>>> i have an hptrr controller with 12-16 2tb satas on it.  a picture
>>> before i started cleaning up some disk failures.
>>>
>>>         NAME                STATE     READ WRITE CKSUM
>>>         tank                ONLINE       0     0     0
>>>           mirror            ONLINE       0     0     0
>>>             label/m00-d01   ONLINE       0     0     0
>>>             label/m00-d00   ONLINE       0     0     0
>>>           mirror            ONLINE       0     0     0
>>>             label/m01-d00   ONLINE       0     0     0
>>>             label/m01-d01   ONLINE       0     0     0
>>>
>>> the reason i used glabels was because when the system boots or the
>>> controller rescans, it assigns da0 to the first drive it finds alive on
>>> the controller, da1 to the second, etc.
>>>
>>> this means that drive addition or removal changes the daX numbering.
>>>
>>> so the labels are so that zfs can find its ass when assembling the
>>> array.
>>
>> Can you use GPT for partitioning? Put a single partition on each disk  
>> and
>> set the GPT label (which is not the glabel). See gpart's add and modify
>> subcommands.
>>
>> 	NAME                          STATE     READ WRITE CKSUM
>> 	gs1p                          ONLINE       0     0     0
>> 	  mirror                      ONLINE       0     0     0
>> 	    gpt/CONST_2-9XE02KPK-zfs  ONLINE       0     0     0
>> 	    gpt/SAVVIO-6XQ10F80-zfs   ONLINE       0     0     0
>> 	    gpt/SAVVIO-6XQ103C7-zfs   ONLINE       0     0     0
>
> ok.  sure i could do that.  but what's the win?
>
> randy

Glabel is FreeBSD only. GPT is standardized. So if you import your pool in  
Solaris it will work with GPT, but not with glabel.

But in your original question I don't really understand your problem with  
glabel (glabel solves the problem of changing da* numbering), so what do  
you want to win?

Ronald.