HP StorageWorks Clustered File System 3.6.0 Windows Storage Server Edition Administration Guide (403103-005, January 2008)

Chapter 8: Configure Dynamic Volumes 91
Duplicate. The volume cannot be reassembled because more than one
physical device matched a logical subdevice specification. Potential
causes of this problem are:
• Both sides of a mirror were exposed (that is, lunmasked) to the cluster.
• One of the devices is a snapclone of the other.
• One of devices is a disk copy or block-level backup/copy of the other.
Truncated. The volume cannot be reassembled because one of the
physical devices is smaller than its logical subdevice specification.
Potential causes of this problem are:
• The disk partition table was changed.
• The size of the LUN was reduced on the array.
Incomplete. The volume cannot be reassembled because one or more of
its subdevices were not found. Potential causes of this problem are:
• The missing subdevices are on LUNs that are not accessible from the
cluster.
• The physical devices containing the logical subdevices were
overwritten.
Reuse Subdevices in Unimportable Volumes
The subdevices in an unimportable volume can be reused in other
dynamic volumes or filesystems after the original volume is destroyed.
This step removes the volume signature from all of the subdevices,
freeing them for other uses.
On the HP Management Console, when you select a subdevice from an
unimportable volume for use in a new filesystem or a new or extended
volume, the console will report that the subdevice contains a volume
signature and will ask whether you want to destroy the associated
dynamic volume. This operation will succeed for both the incomplete and
truncated states. If the volume is in the duplicate state, the operation will
fail and you will need to run the corresponding mx command with the --
reuse option.