Phantom metaset

Howdy,

While reviewing our device groups today, I noticed that cldg is reporting a metaset we deleted quite some time ago:

$ cldg status

=== Cluster Device Groups ===

Device Group Status

Device Group NamePrimarySecondaryStatus

---

webdg-- Offline

shellset snode2snode1Online

apacheset -- Offline

oracleset snode1snode2Online

$ metaset

Set name = shellset, Set number = 2

HostOwner

snode1

snode2 Yes

Mediator Host(s)Aliases

snode1

snode2

Driv Dbase

d3Yes

Set name = apacheset, Set number = 3

HostOwner

snode1

snode2

Driv Dbase

d4Yes

Set name = oracleset, Set number = 4

HostOwner

snode1

snode2

Driv Dbase

d5Yes

d6Yes

Does anyone know how to get rid of this?

Thanks for any insight,

- Ryan

[933 byte] By [matty_91a] at [2007-11-27 2:04:58]
# 1
Oooops -- I forgot to mention that "webdg" is the phantom.- Ryan
matty_91a at 2007-7-12 1:49:42 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...
# 2
Ideally on deletion, CCR would have also got updated. Have you tried the metaset command on all the member nodes?You can try this harmless command to see if it is a question of syncing: cldg sync +
maddy@suna at 2007-7-12 1:49:42 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...
# 3
Yup. None of the cluster nodes show webdg in their metaset output. - Ryan
matty_91a at 2007-7-12 1:49:42 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...