Contact Us

Home > Error Running > Error Running Vxprint Command For Volume

Error Running Vxprint Command For Volume

It is possible that updates have been made to the original version after this document was translated and published. Make the following change and attempt to run vxresize again:# export PATH="$PATH:/opt/VRTS/bin"# /etc/vx/bin/vxresize -b -x -g datadg datavolume +20gIf this continues to fail it is possible that fsadm is terminating incorrectly You may also refer to the English Version of this knowledge base article for up-to-date information. It is possible that updates have been made to the original version after this document was translated and published. Source

No Yes Veritas Volume Manager known issues The following issues were reported for this release of VxVM. Hitachi arrays in Active/Active mode When Hitachi DF400 and DF500 arrays are configured in Active/Active mode, performance is degraded. [73154] Adding HP-EVA disks When HP-EVA disks are added to VxVM 5.0, Use the following commands to check the status of the volume or disks: # iostat –En (for possible io errors) # vxdisk list # echo | format (for disk errors) # After a layered volume is resized, the volume, plex and subdisk names associated with the subvolumes, are changed.

Vendors of disk arrays may also provide capabilities that require special licenses for certain features of their hardware. [137185] Miscellaneous issues Disks with write-back caches Disk drives configured to use a In a clustered or HA environment where Veritas Cluster Server agents need to communicate with vxconfigd to determine the health of VxVM components, service groups start timing out and failing. The naming scheme that is in operation can be deduced from the output to the vxdisk list command. [611320] vxdiskadm displays error V-5-1-9764 when excluding devices The vxdiskadm operation displays error WARNING: VxVM vxio V-5-0-23 Open on an spurious volume device (hex_id) encountered.

This can potentially cause two kinds of problem: The node becomes unavailable for VxVM administrative commands. Cache volumes in volume sets Do not add cache volumes (used by space-optimized instant snapshots) to volume sets. To upgrade a disk group, use the following command: # vxdg [-T version] upgrade diskgroup Unless a disk group version is specified, this command upgrades the disk group to the highest No Yes Did this article save you the trouble of contacting technical support?

As a result, the volume states can become inconsistent and a subsequent vxvol init command might fail. In fact, the operation fails. [565072] Maximum size of a volume The maximum size of a volume is shown as a rounded-down integer number of gigabytes. Create/Manage Case QUESTIONS? In particular, auto-discovered attributes such as DiskGroup and Enclosure are not translated. [139162] Inaccuracies in ISP attribute fields The ISP User Template Wizard shows two "attribute value" fields rather than one

Workaround: When executing the vxvol or vxmend command on a layered volume, first issue the command to the lower level volumes in a bottom-up fashion; then execute the command on the Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? VXVM 2012-07-12 Lingeswaran R Share Facebook Google + LinkedIn Tags VXVM Previous how to configure Sun X86 Blade ILOM ? One of the following messages is displayed as a result of a failed disk group split, join or move operation: There are volume(s) with allsites flag which do not have a

The system returned: (22) Invalid argument The remote host or network may be down. For example, you need a full Veritas Volume Manager license to use the instant snapshot feature. But i just shared high plan to fix the volume issues.Please go through the steps and let me know if you have any doubt by adding comment on this article.

Controller states Controller states may be reported as ''Not Healthy'' when they are actually healthy, and ''Healthy'' when they are actually not healthy. [599060] Remote Mirror (campus cluster) There is no

This is because the joining node does not have any knowledge of the cluster configuration before the join takes place, and it attempts to use the primary path for I/O. this contact form Device issues Unsupported disk arrays To ensure that DMP is set up correctly on a multiported JBOD or other disk array that is not supported by VxVM, use the procedure given No Yes How can we make this article more helpful? Next How to cleanup veritas volume manager device tree ?

The workaround is to use the vxassist addlog command to add a DRL log plex, or the vxsnap command to add a version 20 DCO plex at the specified site (site=sitename). This causes data corruption and system panics. [614061, 614787] Intelligent Storage Provisioning issues Creating application volumes To create application volumes successfully, the appropriate licenses must be present on your system. The messages typically include information about the device offset and disk access name affected by the failure. CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical

The cache object, but not the cache volume, is visible in the graphical interface. Veritas does not guarantee the accuracy regarding the completeness of the translation. Cloudscraper May 31, 2016 Deploying Openstack on Redhat - Packstack Method (Mitaka) May 30, 2016 Managing Zone Cluster - Oracle Solaris April 13, 2016 Powered by WordPress UnixArena by Lingeswaran R

Each VxVM release supports a specific set of disk group versions and can import and perform tasks on disk groups with those versions.

Before replacing such a failed disk, use the following commands to set the correct site name on the replacement disk: # vxdisk -f init disk # vxdisk settag disk site=sitename [536853, The message is erroneous, and it is safe to continue the operation. [575262] Failures when importing disk groups Messages about failures to import disk groups are not displayed by the Web Failing to take these precautions can result in unknown system behavior or lock-up. [6154] Adding a log and mirror to a volume The vxassist command does not add a mirror and In this example, a volume, vol, has two subvolumes, vol-L01 and vol-L02.

stop and restart had. If the Volume is in DISABLED ACTIVE state and the Plex in DISABLED RECOVER: ·        The plex state can be stale, empty, nodevice, etc. See the nsswitch.conf(4) manual page. Check This Out In rare cases you may need to face such a issues due environment(Like SAN issue),volume may go in to I/O error state or LUN paths will be disconnected to the server.However

This contradicts the normal rule that only disk groups that are (non-temporarily) imported at the time of a crash are auto-imported. If the script reports that any disks need to be re-initialized, back up the file systems and data residing on the volumes on those disks, and restore them after re-initializing the This may occur if the disks previously belonged to disk groups in older releases of VxVM. Sorry, we couldn't post your feedback right now, please try again later.

Grow the file system hosted on that volume (fsadm)The error message above should be presented as a pair of messages, first the error message generated by the fsadm command, and second Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem When deporting a disk group, the following error comes up: "vxvm:vxdg: ERROR: Disk group Generated Fri, 14 Oct 2016 19:13:00 GMT by s_ac15 (squid/3.5.20) This value is usually 231-1 bytes (1 byte less than 2 terabytes).

To see the current cluster protocol version, type: # vxdctl support To upgrade the protocol version for the entire cluster, enter the following command on the master node: # vxdctl upgrade This causes any ongoing operation, such as a resynchronization, to fail. For shared disk groups, the latest disk group version is only supported by the latest cluster protocol version. 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.

The system returned: (22) Invalid argument The remote host or network may be down. Resizing a volume set with an unmounted file system It is not possible to use the vxresize command to change the size of a component volume of a volume set that Are you sure you want to disable it? Thank You!

Once the disk group has been imported successfully, there should be no problem in accessing its volumes. However, if an SFCFS file system is not mounted, it is likely that the fsck of the snapshot will take longer than is usually necessary, depending on the I/O activity at In this case, you have to use vxassist convert to restore the volume to its original layout. Thank You!

The old_layout attribute is no longer supported.