JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Solaris Volume Manager Administration Guide
search filter icon
search icon

Document Information


1.  Getting Started With Solaris Volume Manager

2.  Storage Management Concepts

3.  Solaris Volume Manager Overview

4.  Solaris Volume Manager for Sun Cluster (Overview)

5.  Configuring and Using Solaris Volume Manager (Scenario)

6.  State Database (Overview)

7.  State Database (Tasks)

8.  RAID-0 (Stripe and Concatenation) Volumes (Overview)

9.  RAID-0 (Stripe and Concatenation) Volumes (Tasks)

10.  RAID-1 (Mirror) Volumes (Overview)

11.  RAID-1 (Mirror) Volumes (Tasks)

12.  Soft Partitions (Overview)

13.  Soft Partitions (Tasks)

14.  RAID-5 Volumes (Overview)

15.  RAID-5 Volumes (Tasks)

16.  Hot Spare Pools (Overview)

17.  Hot Spare Pools (Tasks)

18.  Disk Sets (Overview)

19.  Disk Sets (Tasks)

20.  Maintaining Solaris Volume Manager (Tasks)

21.  Best Practices for Solaris Volume Manager

22.  Top-Down Volume Creation (Overview)

23.  Top-Down Volume Creation (Tasks)

24.  Monitoring and Error Reporting (Tasks)

25.  Troubleshooting Solaris Volume Manager (Tasks)

Troubleshooting Solaris Volume Manager (Task Map)

Overview of Troubleshooting the System

Prerequisites for Troubleshooting the System

General Guidelines for Troubleshooting Solaris Volume Manager

General Troubleshooting Approach

Replacing Disks

How to Replace a Failed Disk

Recovering From Disk Movement Problems

Disk Movement and Device ID Overview

Resolving Unnamed Devices Error Message

Device ID Discrepancies After Upgrading to the Solaris 10 Release

Recovering From Boot Problems

Background Information for Boot Problems

How to Recover From Improper /etc/vfstab Entries

Recovering the root (/) RAID-1 (Mirror) Volume

How to Recover From a Boot Device Failure

Recovering From State Database Replica Failures

How to Recover From Insufficient State Database Replicas

Recovering From Soft Partition Problems

How to Recover Configuration Data for a Soft Partition

Recovering Storage From a Different System

How to Recover Storage From a Local Disk Set

Recovering Storage From a Known Disk Set

How to Print a Report on Disk Sets Available for Import

How to Import a Disk Set From One System to Another System

Recovering From Disk Set Problems

What to Do When You Cannot Take Ownership of A Disk Set

How to Purge a Disk Set

Performing Mounted Filesystem Backups Using the ufsdump Command

How to Perform a Backup of a Mounted Filesystem Located on a RAID-1 Volume

Performing System Recovery

How to Recover a System Using a Solaris Volume Manager Configuration

A.  Important Solaris Volume Manager Files

B.  Solaris Volume Manager Quick Reference

C.  Solaris Volume Manager CIM/WBEM API


Recovering From Disk Set Problems

The following sections detail how to recover from specific disk set related problems.

What to Do When You Cannot Take Ownership of A Disk Set

In cases in which you cannot take ownership of a disk set from any node (perhaps as a result of a system failure, disk failure, or communication link failure), and therefore cannot delete the disk set record, it is possible to purge the disk set from the Solaris Volume Manager state database replica records on the current host.

Purging the disk set records does not affect the state database information contained in the disk set, so the disk set could later be imported (with the metaimport command, described at Importing Disk Sets).

If you need to purge a disk set from a Sun Cluster configuration, use the following procedure, but use the -C option instead of the -P option you use when no Sun Cluster configuration is present.

How to Purge a Disk Set

  1. Attempt to take the disk set with the metaset command.
    # metaset -s setname -t -f

    This command will attempt to take (-t) the disk set named setname forcibly (-f). If the set can be taken, this command will succeed. If the set is owned by another host when this command runs, the other host will panic to avoid data corruption or loss. If this command succeeds, you can delete the disk set cleanly, without the need to purge the set.

    If it is not possible to take the set, you may purge ownership records.

  2. Use the metaset command with the -P to purge the disk set from the current host.
    # metaset -s setname -P

    This command will purge (-P) the disk set named setname from the host on which the command is run.

  3. Use the metaset command to verify that the set has been purged.
    # metaset

Example 25-5 Purging a Disk Set

host1# metaset -s red -t -f
metaset: host1: setname "red": no such set
host2# metaset

Set name = red, Set number = 1

Host                Owner

Drive    Dbase

c1t2d0   Yes  

c1t3d0   Yes  

c1t8d0   Yes  

host2# metaset -s red -P
host2# metaset
See Also