VxVM vxvol ERROR V-5-1-1259 Volume swapsan violates swap usage type restrictions.
VxVM vxvol ERROR V-5-1-1259 Volume swapsan violates swap usage type restrictions, cannot be started VxVM vxassist ERROR V-5-1-506 Could not initialize volume swapsan.
Explanation of this error condition.:
cfs14.engba.symantec.com: vxassist -g slicedg -U swap make svol6 30g
VxVM vxvol ERROR V-5-1-1259 Volume svol6 violates swap usage type
restrictions,
cannot be started
VxVM vxassist ERROR V-5-1-506 Could not initialize volume svol6
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)
In your case, a secondary swap area is being added. So the workaround used
is fine.
Why does VxVM warn when adding secondary swap ? Partly because when
creating the volume, we have no idea how its intended to be used.
The customer believes that we should refine this so as not to create an
issue when adding a secondary swap area.
Our internal testing showed we got this error consistently when using thin
luns.
Comments
John, Your description of the
John,
Your description of the problem isn't very clear.
From what I gather the customer is seeing issues while adding a secondary swap area, either be it on a non-rootdg or a thin lun.
Please file an etrack incident.
Would you like to reply?
Login or Register to post your comment.