Solaris Volume Manager (SVM) Metadb Statedatabase, Error on Bad or Corrupt, Replica, Repair, State Database Resolution Path (Doc ID 1501153.1)

Last updated on APRIL 29, 2024

Applies to:

Purpose

This document is a Resolution Path.  It aids in troubleshooting of metadb state database, metadb, state database, statedatabase, replica issues.

The following problems are addressed in this document:

1) How to validate SVM packages are installed.

2) How to display the locations and status of the current metastate databases.

3) How to confirm metastate databases are not part of SVM metaset.

4) How to verify underlying disks are accessible and healthy

5) Problems while repairing/adding SVM databases

6) Recovering From Insufficient Metadevice State Database Replicas

7) Creating replica database via metadb command returns I/O error

8) Sizes Of State Database Replicas

9) Panics related to metastate database issue.

10) Local filesystems on Solaris 10 may not be mounted at boot if they have been built on iscsi luns
or other fabric attached luns if Solaris Volume Manager metadbs are placed on those luns

Example errors:

metainit: demo: stale databases

Insufficient metadevice database replicas located.

Use metadb to delete databases which are broken.

metadb: hostname: cNtNdNsN: overlaps with cNtNdNsN which is mounted as '/'

metadb: hostname: /dev/rdsk/cNtNdNsN: I/O error

metadb:  hostname:  cNtNdNsN:  device size xxxx is too small for metadevice database replica

panic string:   md: Panic due to lack of DiskSuite state database replicas. Fewer than 50% of the total were available, so panic to ensure data integrity.

panic[cpu0]/thread=180e000: vfs_mountroot: cannot remount root


Background:

Solaris Volume Manager, SVM and Solstice DiskSuite Software, SDS metadumpdb: Usage and metadb Replica Layout (Doc ID 1003492.1)

Troubleshooting Steps

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.