Sol10: All submirrors "Need Maintenance" after clean reboot
On all my Solaris 10 boxes, after a clean reboot, all submirrors "need maintenance". A metasync immediately clears the problem. Is this a bug or a feature?
d0: Mirror
Submirror 0: d10
State: Needs maintenance
Submirror 1: d20
State: Needs maintenance
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 32534744 blocks (15 GB)
d10: Submirror of d0
State: Needs maintenance
Invoke: metasync d0
Size: 32534744 blocks (15 GB)
Stripe 0:
DeviceStart Block DbaseState Reloc Hot Spare
c0t0d0s0 0NoOkayYes
[etc]
[646 byte] By [
wsanders] at [2007-11-26 9:48:30]

# 1
Found this summary in sunmanagers:
http://www.sunmanagers.org/pipermail/summaries/2005-June/006531.html
Basically, for the volume manager to work right, I have to enable rpcbind.
Is rpcbind still full of huge security holes?
No luck getting rpc.metad to run standalone.
I suppose I need to install tcpwrappers.
# 3
Another workaround, from
http://72.14.209.104/search?q=cache:QoKwy4SOZL0J:www.sunmanagers.org/pipermail/ summaries/2006-February/007079.html+%22Solaris+10%22+%22Needs+maintenance%22& ;hl=en&gl=us&ct=clnk&cd=1
Although none of my systems have mdmonitord registered as a service:
# svcadm enable mdmonitord
svcadm: Pattern 'mdmonitord' doesn't match any instances
DISABLING rpc/meta is what allows /usr/sbin/mdmonitord to startup correctly, WITHOUT rpc.metad, and this makes the submirrors come up in sync.