Solaris Volume Manager (SVM) metastat Command Shows Soft Partition in Errored State

(Doc ID 1010479.1)

Last updated on JANUARY 17, 2017

Applies to:

Sun Solaris Volume Manager (SVM) - Version 11.9.0 to 11.11 [Release 11.0]
Solstice DiskSuite Software - Version 4.2.1 to 4.2.1 [Release 4.0]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on x86 (32-bit)

Symptoms

In the following example, all access to application data is failing. The data set resides on a device managed by the soft partitioning feature of Solaris Volume Manager (SVM). Everything is failing with an I/O error.

# df -k /data-84
   df: (/data-84) not a block device, directory or mounted resource

 

# cp /database /data-84
  cp: cannot create /data-84: I/O error


When you look at underlying device with metastat, you will discover a layered metadevice. d84 is a soft partition created from d80 which in turn is created from disk slice c0t12d0s0. This creation technique is not in line with best practices in
<Document 1417827.1> Solaris Volume Manager (SVM): Best Practices for Creation and Implementation of Soft Partitions
but none the less allowed. (d84 could be created directly from c0t12d0s0). This adds an extra layer of complexity to the problem at hand.

# metastat
d84: Soft Partition
    Device: d80
    State: Errored
    Size: 8388608 blocks (4.0 GB)
        Extent              Start Block              Block count
             0                       32                  8388608

d80: Concat/Stripe
    Size: 17465344 blocks (8.3 GB)
    Stripe 0:
        Device      Start Block  Dbase        State Reloc Hot Spare
        c0t12d0s0          0     No            Okay   Yes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms