To encapsulate a volume

1. List the volumes:

     # vxvset -g dg1 list myvset
     VOLUME   INDEX   LENGTH   STATE   CONTEXT
     vol1     0       102400   ACTIVE  -
     vol2     1       102400   ACTIVE  -

   The volume set has two volumes.

2. Create a third volume and copy the passwd file to the third volume:

     # vxassist -g dg1 make dbvol 100m
     # dd if=/etc/passwd of=/dev/vx/rdsk/rootdg/dbvol count=1
     1+0 records in
     1+0 records out

   The third volume will be used to demonstrate how the volume can be accessed as a file, as shown later.

3. Create a file system on the volume set:

   On AIX:

     # mkfs -V vxfs /dev/vx/rdsk/rootdg/myvset
     version 7 layout
     204800 sectors, 102400 blocks of size 1024,
     log size 1024 blocks
     largefiles supported

   On HP-UX and Solaris:

     # mkfs -F vxfs /dev/vx/rdsk/rootdg/myvset
     version 7 layout
     204800 sectors, 102400 blocks of size 1024,
     log size 1024 blocks
     largefiles supported

   On Linux:

     # mkfs -t vxfs /dev/vx/rdsk/rootdg/myvset
     version 7 layout
     204800 sectors, 102400 blocks of size 1024,
     log size 1024 blocks
     largefiles supported

4. Mount the volume set:

   On AIX:

     # mount -V vxfs /dev/vx/dsk/rootdg/myvset /mnt1

   On HP-UX:

     # mount -F vxfs /dev/vx/dsk/rootdg/myvset /mnt1

   On Linux:

     # mount -t vxfs /dev/vx/dsk/rootdg/myvset /mnt1

   On Solaris:

     # mount -F vxfs /dev/vx/dsk/rootdg/myvset /mnt1

5. Add the new volume to the volume set:

     # vxvset -g dg1 addvol myvset dbvol

6. Encapsulate dbvol:

     # fsvoladm encapsulate /mnt1/dbfile dbvol 100m
     # ls -l /mnt1/dbfile
     -rw------- 1 root other 104857600 May 22 11:30 /mnt1/dbfile

7. Examine the contents of dbfile to see that it can be accessed as a file:

     # head -2 /mnt1/dbfile
     root:x:0:1:Super-User:/:/sbin/sh
     daemon:x:1:1::/:

   The passwd file that was written to the raw volume is now visible in the new file.

   Note:

   If the encapsulated file is changed in any way, such as if the file is extended, truncated, or moved with an allocation policy or resized volume, or the volume is encapsulated with a bias, the file cannot be de-encapsulated.