Hi Jeff
From the above output, I would understand that "offset" actually defines the offset from where the region is starting. so public offset would say that public offset is starting from 65774 & spanning to length of 943652560 ... & for private ,offset is starting from 208 & spanning to a length of 65536.
If we see the man page for vxdisksetup:
puboffset=offset
-- Sets the offset on the disk where the public region starts. By default, this is past the end of the private region.
For the sliced format, 256 blocks of disk space (rounded up to the nearest cylinder boundary) are reserved at the beginning of the public region unless this is overridden by the value of puboffset. The reserved space allows for later conversion to the cdsdisk format.
For the simple format, 256 blocks of disk space are reserved at the end of the private region unless this is overridden by the value of puboffset. The reserved space allows for later conversion to the cdsdisk format.
For cdsdisk format disks, puboffset is silently rounded up to the nearest multiple of 8KB if it is not already a multiple of 8KB.
For disk_offset, I believe it is a sector value only.... chk this e.g
# prtvtoc -h /dev/rdsk/c3t5d23s2
|
* First Sector Last
|
|
* Partition Tag Flags Sector Count Sector Mount
|
|
2 5 01 0 238091520 238091519
|
|
3 15 01 0 3840 3839
|
|
4 14 01 3840 238087680 238091519
|
# vxdisk list c1t5d23 | egrep "public:|private:"
|
public: slice=4 offset=0 len=238087680 disk_offset=3840
|
|
private: slice=3 offset=1 len=3839 disk_offset=0
|
After a successful initialization we have matching sizes:
Total available disk space using "vxdisk list " output = 238087680(len) + 3840 (disk_offset)
= 238091520 sectors
Total available disk space using "prtvtoc -h " output = 238091520 (Sector count)
Gaurav
