Board index Solaris

state databases in shared disk set

state databases in shared disk set

Post by noon » Wed, 23 Feb 2005 17:53:43



I currently just have one host added to a shared disk set. Another host
will be added later.

Questions:

1) With shared disk sets, s7 on all disks in the diskset is used to
store the state databases of the shared disk set. What procedure is then
required when replacing a faulty disk in the disk set ?

I assume that you have to delete the disk from the disk set first, then
after replacing it with a new disk, add the new disk to the disk set ...
BUT ... can you actually delete a faulty disk from the disk set ( will
metaset -s setname -d cxtxdx fail if the disk is faulty ) ?

2) Also, when I run "metaset -s <setname>", at the end, you have:

Device Relocation Information:
Device   Reloc  Device ID





Is this "Device Relocation Information" also stored on the disks in the
shared diskset ? If it is, how does replacing a faulty disk affect this
information ?

 
 
 
Top

state databases in shared disk set

Post by noon » Wed, 23 Feb 2005 17:54:59


Accidentally clicked post.

3) What purpose does the local state database that is stored in the
internal disks serve ?

 
 
 
Top

state databases in shared disk set

Post by noon » Wed, 23 Feb 2005 18:06:31



> 2) Also, when I run "metaset -s <setname>", at the end, you have:

> Device Relocation Information:
> Device   Reloc  Device ID





> Is this "Device Relocation Information" also stored on the disks in the
> shared diskset ? If it is, how does replacing a faulty disk affect this
> information ?

Also just realised that, I actually have 6 disks in the diskset:

# metadb -s shared3310
         flags           first blk       block count
      a m     luo        16              8192            /dev/dsk/c2t0d0s7
      a       luo        16              8192            /dev/dsk/c2t0d1s7
      a       luo        16              8192            /dev/dsk/c2t0d2s7
      a       luo        16              8192            /dev/dsk/c2t0d3s7
      a       luo        16              8192            /dev/dsk/c2t0d4s7
      a       luo        16              8192            /dev/dsk/c2t0d5s7

However, that "Device Relocation Information" does not show c2t0d5.
Is that a concern ?

 
 
 
Top

state databases in shared disk set

Post by Jorgen Moquis » Thu, 24 Feb 2005 07:19:34




>> 2) Also, when I run "metaset -s <setname>", at the end, you have:

>> Device Relocation Information:
>> Device   Reloc  Device ID





>> Is this "Device Relocation Information" also stored on the disks in
>> the shared diskset ? If it is, how does replacing a faulty disk affect
>> this information ?

> Also just realised that, I actually have 6 disks in the diskset:

> # metadb -s shared3310
>         flags           first blk       block count
>      a m     luo        16              8192            /dev/dsk/c2t0d0s7
>      a       luo        16              8192            /dev/dsk/c2t0d1s7
>      a       luo        16              8192            /dev/dsk/c2t0d2s7
>      a       luo        16              8192            /dev/dsk/c2t0d3s7
>      a       luo        16              8192            /dev/dsk/c2t0d4s7
>      a       luo        16              8192            /dev/dsk/c2t0d5s7

> However, that "Device Relocation Information" does not show c2t0d5.
> Is that a concern ?

see man metadevadm /j?rgen
 
 
 
Top

state databases in shared disk set

Post by noon » Thu, 24 Feb 2005 10:35:19





>>> 2) Also, when I run "metaset -s <setname>", at the end, you have:

>>> Device Relocation Information:
>>> Device   Reloc  Device ID





>>> Is this "Device Relocation Information" also stored on the disks in
>>> the shared diskset ? If it is, how does replacing a faulty disk
>>> affect this information ?

>> Also just realised that, I actually have 6 disks in the diskset:

>> # metadb -s shared3310
>>         flags           first blk       block count
>>      a m     luo        16              8192            /dev/dsk/c2t0d0s7
>>      a       luo        16              8192            /dev/dsk/c2t0d1s7
>>      a       luo        16              8192            /dev/dsk/c2t0d2s7
>>      a       luo        16              8192            /dev/dsk/c2t0d3s7
>>      a       luo        16              8192            /dev/dsk/c2t0d4s7
>>      a       luo        16              8192            /dev/dsk/c2t0d5s7

>> However, that "Device Relocation Information" does not show c2t0d5.
>> Is that a concern ?

> see man metadevadm /j?rgen

Thanks. Just realised that I actually have not created a metadevice on
c2t0d5, and hence, not Device Relocation Information.
 
 
 
Top

1. State Database and State Database Replicas problem?

Hello all,
I am trying to figure out why when I created 4 extra state databases on
the second disk the metadb is saying that they are marked with "r".Which
means r - replica does not have device relocation information.

Here it is my senario. I have a V480 server with 2 disks and solaris 9
12/02 installed in the first disk.
I created 2 partitions in each disks slice6 and slice 7.
I create the meta database like this
metadb -a -f -c2 c1t0d0s6 c1t0d0s7
metadb -a -c2 c1t1d0s6 c1t1d0s7
and when I run metadb -i I see that in the state databases for the
second disk has the flug "r",all states has the flug "u".

Is this normal?

Regards,
Pavlos

2. Problems with installing Linuy on 164UX

3. Stabbed US preacher flees INDIA state (The same INS tactics used against the stabbed preacher)

4. NN thrashes .newsrc file (esp over NFS)

5. Disk sets: databases always stale after reboot?

6. Deciphering An Error Message...

7. Solaris 10 x86: Constructing a shared disk set between two hosts

8. How to set FQDN (RedHat 6.2)?

9. How to make a bootimage disk, like the bootdsks.144 ins slackware.

10. Setting up firewall for dial-ins: How?

11. Need Help on setting up getty for dial-ins

12. Setting up Ctrl-Alt-Ins = halt

13. State Database Replicas


All times are UTC
Board index