In such a case, use the vxassist convert to restore the volume to its original layout.Īfter a layered volume is resized, the volume names, the plex names and the subdisk names associated with the subvolumes, are changed. If the system reboots before the grow or shrink of a layered volume completes, the volume is left with an intermediate layout. This causes any ongoing operation, such as the resynchronization, to fail. Internally, Volume Manager converts the layout of layered volumes and updates the configuration database before it shrinks or grows their sizes. Note that this limitation does not apply to ISP layered volumes. Resizing layered volumes during resynchronizationĭue to the current implementation to handle the resize of layered volumes, it is recommended that you do not grow or shrink layered volumes (stripe-mirror, concat-mirror, and so on) while resynchronization is ongoing. # vxvol -g diskgroup set allsites=on volume Turn on the allsites attribute for the volume:.# vxassist -g diskgroup mirror volume nmirror= N \ Replace the removed plexes using storage at the remote site:.Use the vxresize command to resize the volume.# vxassist -g diskgroup remove mirror volume \ # vxvol -g diskgroup set allsites=off volume Turn off the allsites attribute for the volume:.If a volume in a Remote Mirror configuration has detached plexes at a remote site, you can use the following procedure to resize it: Resizing volumes with detached remote plexes This value is usually 231-1 bytes (1 byte less than 2 terabytes). However, any 32-bit legacy applications that use system calls such as seek, lseek, read and write are limited to a maximum offset that is determined by the operating system. VxVM supports volume lengths up to 256TB. The workaround is to reinitialize the disks before creating the disk group (for example, by using the vxdisk -f init command), or to use the vxdg adddisk command to add the disks to the disk group after it has been created. This may occur if the disks previously belonged to disk groups in older releases of VxVM. #Failed root disk using veritas volume manager manualThe enclosure attribute should be used to specify an enclosure name to the vxdmpadm getportids command, instead of the enclr attribute that is shown in the Veritas Volume Manager Administrator's Guide and the vxdmpadm(1M) manual page.ĭisk group is disabled if private region sizes differĪ disk group is disabled if the vxdg init command is used to create it from a set of disks that have pre-existing private regions that differ in size. Specifying an enclosure to the vxdmpadm getportids command The error is not seen if controller or device names are specified instead. This error is harmless and can be ignored. The vxdiskadm operation displays error V-5-1-9764 if a vendor and product ID combination are specified to exclude devices from multipathing. Vxdiskadm displays error V-5-1-9764 when excluding devices The naming scheme that is in operation can be deduced from the output to the vxdisk list command. There is no option in the vxddladm command to display the current naming scheme. The Global Device Naming (GDN) option to the vxddladm command should only be used with the Storage Foundation Volume Server software. These operations can result in data loss if used incorrectly. Alternately, you can use vxdiskunsetup(1M) to remove the disks from Volume Manager control. After the installation, if you no longer desire to use those disk groups, use the destroy option of the vxdg(1M) command to remove those disk groups. An attempt during the installation to initialize disks that were previously under Volume Manager control fails. If the disks were previously under Volume Manager control and were used on the same host system, and if the proper uninstall procedures were not followed, the disk groups they represent are imported automatically during the installation process. Make a note of any of the disks that you are planning to initialize if they were previously under Volume Manager control. Reinitializing disks previously under Volume Manager control It should be used only by a system administrator who is trained and knowledgeable about Volume Manager. This command permanently removes a disk from Volume Manager control. # /usr/lib/vxvm/bin/vxdiskunsetup hdisk_N Use the low-level command, vxdiskunsetup, as follows: You can permanently remove this disk from Volume Manager control by removing the VM metadata partition from that disk. Remove a VM disk from a disk group after evacuating any data on the disk. Removing a disk from Volume Manager control Refer to the Veritas Storage Foundation Installation Guide for instructions on upgrading an existing system on which Volume Manager is installed. The following incidents were reported for this release of VxVM.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |