Вы находитесь на странице: 1из 1

Archive for the veritas volume manager Category Creating Veritas Volume using vxmake Posted July 13,

2012 Filed under: veritas volume manager | Leave a Comment We will see how to create a veritas volume using vxmake command. There are two w ays to create a vx volume. A top to bottom approach wherein you create a volume and veritas creates the plex and subdisk for you. A bottom to top approach where in you create the objects and then build a volume. On a comparative note, vxass ist is the easier way as it creates the volume top to bottom. Vxmake is comparat ively difficult to manage in a production environment.. Knowing how to build a volume from scratch does not hurt and is a good exercise in learning the building blocks of VX. Let s see in detail how it works out. vxmak e allows you to create objects individually. The approach will be to create Subdisks, associate plex with subdisk and put the plex in the volume. I am assuming that the disk test01 is part of the testdg di skgroup. 1. Create the Subdisk; #vxmake sd test01-01 test01,0,104857600 ( The value is in sectors ) 2. Build the Plex ; # vxmake plex testplex 3. Associate the Plex with subdisk ; # vxsd assoc testplex test01-01 assoc indicates we are associating the subdisk to the plex. 4. Attach the plex to volume ; # vxmake -U fsgen vol testvol plex=testplex 5. Check the status of the Objects. # vxprint -g testdg -hrtdg testdg default default 0 dm test01 c1t0d0s2 sliced 2048 104857600 v testvol fsgen DISABLED EMPTY 104857600 ROUND pl testplex testvol DISABLED EMPTY 104857600 CONCAT RW sd test01-01 testplex test01 0 104857600 0 c1t0d0 ENA 6. Start the volume ; # vxvol -g testdg start testvol 7. Check the status ; #vxprint -g testdg -hrt Missing Volboot file in VxVM Posted July 3, 2012 Filed under: veritas volume manager | Leave a Comment How to recover from a missing /etc/vx/volboot file? The volboot is an important file, it contains the hostid of the system and this is used by VxVM to establish the ownership of disks. The volboot is important in the management of vxconfigd as well. If the rootdisk is under VxVM control it a lso has the information of boot disk group information. During boot up, vxvm config dameon reads the volboot file, if the file is missin g, vxconfigd fails and the boot sequence is aborted. Solution will be a) to copy the volboot file from backup and reboot the system. b) If a valid backup is not available we may need to run the sequence of command s to enable it again. Obtain the hostid of the system from vxprivutil. # vxprivutil list /dev/dsk/c0t1d0s3 |grep -i hostid # vxdctl stop ( stop the vxconfigd, if its running ) # vxiod set 10 # vxconfigd -m disable ( start the vxconfigd in disable mode ) # vxdctl init <hostid> ( hostid obtained from vxprivutil, this will recreate the /etc/vx/volboot file ) cfgadm:::Device being used by VxVM