vxdisksetup format=sliced|simple|cdsdisk ? what are the differences?

[cowboycraig]

vxdisksetup format=sliced|simple|cdsdisk ? what are the differences?

I cannot find a definition for each type of format.

cdsdisk seems straight forward, that is concantinated. So the data and partitions stay intact.

But I don't really get sliced and simple.

What I am wondering is why I can only (on 4.1) vxrootmir rootdisk when i have:
vxdisksetup -i c1t0d0 format=sliced

If I try that with with a cdisk it fails.

So todo this step I need sliced, and am not sure why.
Re-attach the mirror in the correct order according to the partition layout:
 vxrootmir rootdisk
 vxassist -g rootdg mirror swapvol rootdisk
 vxassist -g rootdg mirror var rootdisk


Thanks!
Craig

[springer]

hi

cds is default from 4.0 onwards it cross platform format aka deport dg from aix and import to solaris stec


sliced is for rootdg so u cnat have cds for rootdg

simple is not so common aka like emc powerpath uses it

Rich

[sunshine_2]

here is the detailed explanation for each format   

cdsdisk   The disk is formatted as a CDS disk that is  suit-
               able  for  moving between different operating sys-
               tems. This is the default  format  (provided  that
               the  -i  option is used to write the disk header).
               It is not suitable for boot disks.

               Slice 7 is created to hold the private and  public
               regions with all other slices (apart from slice 2)
               zeroed out.  The private region is used by VxVM to
               store  configuration  information, and is followed
               by a public region  from  which  subdisks  can  be
               allocated.

               Note: As the CDS format is applied to  the  entire
               disk and is unsuitable for boot disks, options and
               attributes that relate to  partitions,  slices  or
               booting are not applicable.

             
     none      The disk is unformatted.


      simple    Slice 3 is created to hold the private and  public
               regions with all other slices (apart from slice 2)
               zeroed out.  The private region is used by VxVM to
               store  configuration  information, and is followed
               by a public region  from  which  subdisks  can  be
               allocated.

     sliced    Slices 3  and  4  are  created  to  hold  separate
               private  and  public  region  partitions  with all
               other slices (apart  from  slice  2)  zeroed  out.
               This  format  can  be applied to disks that can be
               used to boot the system.  If the disk is not  ini-
               tialized  as a boot disk, space is reserved on the
               disk to allow it to be converted to cdsdisk format
               if required.