[Ocfs2-users] Heartbeat ID and cloning systems

[Sunil Mushran]

To elaborate, the uuid is set in the superblock of the device. So
if you mirror a ocfs2 volume, well you also get the existing uuid
for free. Just change it using tunefs.

Sunil Mushran wrote:
> # mounted.ocfs2 -d
> Device                FS     UUID                                  Label
> /dev/sdb2             ocfs2  22a625d-acae-5341-9f19-f241347a9ffe   
> mmscratch
>
> Alexei_Roudnev wrote:
>> What is device uuid (as I know, it is global for the cluster)? 
>> Problem is
>> that heartbeat id's must be different on different servers, but they 
>> are the
>> same after system have been cloned (disk was copied and then changed 
>> - IP,
>> host name, and so on).
>>
>> As a result, when I open configfs, I see only 1 record for the heartbeat
>> there, and tests indicate that both hosts uses the same id (even having
>> correct configuration with tifferent node numbers in it)..
>>
>> I cloned hosts, not the file system (I know about FS cloning problem and
>> about device uuid). So, it's another problem.
>>
>> ----- Original Message ----- From: "Sunil Mushran" 
>> <Sunil.Mushran at oracle.com>
>> To: "Alexei_Roudnev" <Alexei_Roudnev at exigengroup.com>
>> Cc: "Peter Santos" <psantos at cheetahmail.com>; 
>> <ocfs2-users at oss.oracle.com>
>> Sent: Monday, November 20, 2006 10:39 AM
>> Subject: Re: [Ocfs2-users] Heartbeat ID and cloning systems
>>
>>
>>  
>>> The heartbeat region id is the same as the device uuid.
>>> One can change the device uuid using tunefs.ocfs2.
>>> Available with ocfs2-tools 1.2.2.
>>>
>>> Alexei_Roudnev wrote:
>>>    
>>>> Hi.
>>>>
>>>> DO you have any idea, how to change default ID which ocfs2 uses as a
>>>>       
>> system
>>  
>>>> id, when running heartbeat (it appear at
>>>> /config/cluster/<cluster>/heartbeat/* )
>>>>
>>>>
>>>> I found that, if I clone server (by disk copy) and then change IP,
>>>> hostnames, etc etc (so they works as 2 different servers),
>>>> heartbeat still uses the same string for the heartbeat, so making 
>>>> OCFSv2
>>>> cluster impossible.
>>>>
>>>> System is SLES9 SP3, but I guess that it do not depends of it.
>>>>
>>>>
>>>> _______________________________________________
>>>> Ocfs2-users mailing list
>>>> Ocfs2-users at oss.oracle.com
>>>> http://oss.oracle.com/mailman/listinfo/ocfs2-users
>>>>
>>>>       
>>
>>
>> _______________________________________________
>> Ocfs2-users mailing list
>> Ocfs2-users at oss.oracle.com
>> http://oss.oracle.com/mailman/listinfo/ocfs2-users
>>   
>
> _______________________________________________
> Ocfs2-users mailing list
> Ocfs2-users at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-users