metadb question

[coopermarsh]

Hi

Just upgraded to sc3.2 on solaris 9.

the metadb -i -s dg command is reporting on 1st node the following flags

a luo t r

on the 2nd node

a luo r

Could any please explain what is going on?

Many thanks

 

[bfitzmai]

When I run just metadb -i, a table is also printed explaining what each entry stands for. I am not running the same version as you. My table does not have a "t".

a = Replica is Active
l = Locator for Replica was read
u = Replica is up to date
o = Replica active prior to ......
r = Replica does not have device relocation information

 

[Annihilannic]

Just tried on Solaris 10 running SVM 11.10.0 and that doesn't have a "t" either...

Annihilannic.

 

[jad]

We've used metadb ... I have to say i have never completely trusted it since it took out one of our machines ... the I/O controller died and we never could boot the machine again, even if we could get the data back.

We've never had the same trouble with ZFS mirrored disks, we really have tried hard to kill it, and I would recommend this in quite a major way.

 

[dandan123]

t = tagged data is associated with the replica

Tagged data
Tagged data occurs when there are different versions of a
disk set's replicas. This tagged data consists of the set
owner's nodename, the hardware serial number of the owner
and the time it was written out to the available replicas.
The system administer can use this information to determine
which replica contains the correct data.