# make_net_recovery -v -s igniteserver -x inc_entire=rootdgĢ. For example, for a network base recovery: Create recovery image using Ignite-UX recovery command. HP-UX current bundle version of VxVM 4.1 and 5.0 enforces the creation of CDS aligned logical volumes.ġ. The safest method to resolve this alignment problem is taken a system image of the whole rootdg using Ignite-UX recovery commands and rebuild the system from this image. Use Ignite-UX to rebuild the rootdg diskgroup Note that optvol, rootvol and usrvol logical volumes are not multiples of 8 kilobytes (16 blocks). The command will fail with the following message: This command cannot be used on bootable volumes that contains root or swap volume groups. The script uses space availabe as stepping stone to resize the volumes that does not comply with the cDS alignment restrictions. This method requires at least two disks on the diskgroup, with enough free space to hold a copy the largest logical volume of the other. To fix the alignment, run the following command: # vxdg -g your_dg_name set align=1įor no bootable diskgroups, there is a documented procedure to rebuild the affected diskgroup using the vxcdsconvert script to resize the logical volumes. If the disk group is not compatible with the CDS feature, the volumes length and attribute size values must be multiples of 1 block (512 bytes). If a volume is created in a disk group that is compatible with the Cross-platform Data Sharing (CDS) feature, the volumes length and the values of volume attributes that define the sizes of objects such as logs or stripe units, must be an integer multiple of the alignment value of 16 blocks (8 kilobytes). The VERITAS Volume Manager 4.1 Administrators Guide explains why you are getting the error "VxVM vxmake ERROR V-5-1-6642 Length for subdisk is not a multiple of the disk group alignment." Disk Group Alignment Constraints on Volumes Certain constraints apply to the length of volumes and to the numeric values of size attributes that apply to volumes. This error has been reported on VxVM 4.1 and 5.0 diskgroups: vxvm vxmake error v-5-1-6642 length subdisk not multiple of disk group alignment. Symantec Support Document 325187 limitations VxVM vxbrk_rootmir ERROR V-5-2-4020 Attempting to recreate volume meta-data on rootdisk02/c3t15d0 ![]() VxVM vxmake ERROR V-5-1-10127 associating subdisk rootdisk02-07 with optvol-02: Record not in disk group VxVM vxmake INFO V-5-1-9408 Subdisk length is 3592681 while disk group alignment is 8 VxVM vxmake ERROR V-5-1-6642 Length for subdisk rootdisk02-07 is not a multiple of the disk group alignment. VxVM vxbrk_rootmir INFO V-5-2-2566 16:38: Preparing disk c3t15d0 as a VxVM root disk VxVM vxbrk_rootmir INFO V-5-2-4054 16:38: Setting broken off mirror on c3t15d0 as unique root disk VxVM vxbrk_rootmir INFO V-5-2-4022 16:38: Breaking off root mirror on DA c3t15d0 VxVM vxbrk_rootmir INFO V-5-2-4052 16:38: Saving configuration data for later restoration VxVM vxbrk_rootmir INFO V-5-2-4025 16:38: DA c3t15d0, DM rootdisk02 is a valid root mirror VxVM vxbrk_rootmir INFO V-5-2-4023 16:38: Checking specified disk(s) for presence and type # /etc/vx/bin/vxbrk_rootmir -g drd_rootdg -vb c3t15d0 Break the rootdg diskgroup mirror using the vxbrk_rootmir script. VxVM vxrootmir INFO V-5-2-1616 16:36: Disk c3t15d0 is now a mirrored root diskĢ. VxVM vxrootmir INFO V-5-2-2462 16:36: Current setboot values: VxVM vxrootmir INFO V-5-2-1649 16:34: Mirroring volume rootvol VxVM vxrootmir INFO V-5-2-1648 16:33: Mirroring volume standvol VxVM vxrootmir INFO V-5-2-1648 16:28: Mirroring volume optvol VxVM vxrootmir INFO V-5-2-1648 16:27: Mirroring volume varoptvol VxVM vxrootmir INFO V-5-2-1648 16:25: Mirroring volume varcrashvol VxVM vxrootmir INFO V-5-2-1648 16:22: Mirroring volume varvol VxVM vxrootmir INFO V-5-2-1648 16:18: Mirroring volume usrvol VxVM vxrootmir INFO V-5-2-1648 16:16: Mirroring volume tmpvol VxVM vxrootmir INFO V-5-2-1648 16:11: Mirroring volume swapvol VxVM vxrootmir INFO V-5-2-1646 16:11: Mirroring all volumes on root disk VxVM vxrootmir INFO V-5-2-2478 16:11: Disk Media Name rootdisk02 is Disk Access Name c3t15d0 VxVM vxrootmir INFO V-5-2-2441 16:11: Checking specified disk(s) for usability VxVM vxrootmir INFO V-5-2-2501 16:11: Gathering information on the current VxVM root configuration
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |