Error Code details
Severity: n/a 
Component: Volume Manager 
Volume %s violates %s usage type restrictions, cannot be started


Veritas solutions
This UMI code does not yet have a Solution.Click here to issue a request for a Solution. 


User solutions
Solution 1 Vote: [Useful] [Not useful]
Contributed by: Laura Shepard 
Edited: 2010-08-13 15:44:07
Platform: Generic
Release: Generic

Explanation of at least one cause of this error condition, although not a solution:

VXVM checks to see whether the volume being created(with -U swap) spans more than one disk. (We call this a restricted plex check. ie Atleast one plex of the volume contains a single subdisk that spans the entire volume length) This check is necessary for boot disks because the swap area may be required prior to initializing the volume during boot (ie needed before vxvm starts) If the entire volume length is encompassed within one disk, this is not a problem.... However, if the volume contains multiple disks, this will lead to a problem with the swap area on the boot disk. The important take-away is that this a requirement only if the swap volume is the primary swap area (on the boot disk) Its not a consideration when adding secondary swap areas (VxVM will be up when this is needed) Why does VxVM warn when adding secondary swap ? Because when creating the volume, VxVM has no idea how its intended to be used.

See also:


Read and accept Terms of Service