Sponsored Content
Operating Systems Solaris Disks are not visible in Veritas Volume manager Post 303040779 by hicksd8 on Wednesday 6th of November 2019 03:24:39 PM
Old 11-06-2019
My initial thoughts are:

1. Check cabling and disk jumpers for addressing conflicts.
2. Check disk labels are compatible with VCS
3. Check disk mode pages are not left in inconsistent state from previous use.

So (1) speaks for itself. (2) you could rewrite the disk labels to ensure they are compatible with VCS. They probably need to be Sun labels but check that out. (3) disks are highly programmable devices and the mode pages on them can lock a disk out from inquiry from any device other than the one it thinks it's locked to (as in a cluster failover). As you will know, only one node can read and write to any volume at one time otherwise corruption results. This can leave disks in a locked state so select the option "set all mode pages to default" to clear all settings.

So I would look at 1,2,& 3 first. Remember to do both 2 and/or 3 you need to run format in expert mode. By default, Solaris format doesn't offer such menu options. Add the -e switch:

Code:
# format -e

to run format in expert mode. You're telling Solaris that you're an expert so you'd better be one.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to start Veritas volume manager

? (1 Reply)
Discussion started by: 98_1LE
1 Replies

2. UNIX for Dummies Questions & Answers

veritas filesystem and volume manager

WHat is the difference between Veritas filesystem and veritas volume manager? Regards (2 Replies)
Discussion started by: knarayan
2 Replies

3. Filesystems, Disks and Memory

VEritas Volume Manager command

Hi, Somebody can help me to retrieve the command to use in Solaris 8 to display the space free on a Virtual disk created by VVM ? Thanks very much, Fabien Renaux (1 Reply)
Discussion started by: unclefab
1 Replies

4. Solaris

How to resize mirror volume in veritas volume manager 3.5 on Solaris 9 OE

Hi all, I have a problem with vxvm volume which is mirror with two disks. when i am try to increase file system, it is throwing an ERROR: can not allocate 5083938 blocks, ERROR: can not able to run vxassist on this volume. Please find a sutable solutions. Thanks and Regards B. Nageswar... (0 Replies)
Discussion started by: nageswarb
0 Replies

5. UNIX for Advanced & Expert Users

Regarding Veritas Volume manager

hy guys I am new at this thread , i have installed sf 5.0 and wanted to encapsulate root disk but when i get to optionn to enter private region i get this error: Enter desired private region length (default: 65536) 512 VxVM ERROR V-5-2-338 The encapsulation operation failed with the... (2 Replies)
Discussion started by: charneet
2 Replies

6. Solaris

veritas volume manager links

Hi all, Anybody know the URLs of veritas volume manager disk problems,volume problems,root disk problems ...etc. Please share the URL's. i really appreciate for cooperation. regards krishna (4 Replies)
Discussion started by: murthy76
4 Replies

7. Solaris

RAID manager or veritas volume manager

Can somebody kindly help me to determine which one i should choose to better manipulate OS volume. RAID manager or veritas volume manager? Any critical differences between those two? Thanks in advance. (5 Replies)
Discussion started by: beginningDBA
5 Replies

8. Solaris

Veritas volume manager in solaris.

Can you please let me know the certification code for veritas volume manager in solaris ? Thanks in advance. (2 Replies)
Discussion started by: gowthamakanthan
2 Replies

9. UNIX for Dummies Questions & Answers

VERITAS Volume Manager - mirror a disk/volume

I have a machine (5.10 Generic_142900-03 sun4u sparc SUNW,Sun-Fire-V210) that we are upgrading the storage and my task is to mirror what is already on the machine to the new disk. I have the disk, it is labeled and ready but I am not sure of the next steps to mirror the existing diskgroup and... (1 Reply)
Discussion started by: rookieuxixsa
1 Replies

10. UNIX for Beginners Questions & Answers

How to extend a disk in veritas volume manager in veritas cluster?

Hi Experts, I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system. #hastatus -sum -- System State Frozen A node1 running 0 A node2 running 0 -- Group State -- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies
PKGKDE-VCS(1)						  Debian KDE packaging VCS helper					     PKGKDE-VCS(1)

NAME
pkgkde-vcs - a helper tool for Debian pkg-kde VCS repositories. SYNOPSIS
pkgkde-vcs [-vy] subcommand [ SUBCOMMAND OPTIONS ] [ -- EXTERNAL TOOL OPTIONS ] pkgkde-git [-vy] subcommand [ SUBCOMMAND OPTIONS ] [ -- EXTERNAL TOOL OPTIONS ] DESCRIPTION
pkgkde-vcs is a helper tool which aims to simplify a couple of routine tasks associated with packaging management in version control system (VCS) repositories. pkgkde-vcs transparently supports VCSes used by Debian Qt/KDE maintainer groups wrapping various VCS related command sequences into a convenient CLI interface. Please note that this helper enforces the best practises and packaging conventions adopted by Debian Qt/KDE maintainer groups and therefore it should not be considered as a general purpose packaging helper. pkgkde-vcs should be run from the fully checked out packaging repository of the package it is supposed to act upon. Firstly, it attempts to detect a VCS in use for the particular packaging in the working directory. Please note, that the detection might fail if underlying VCS utilities are not installed. If you want or have to force a specific VCS type, run the command as pkgkde-$vcs, for example pkgkde-git. If detection is successful, pkgkde-vcs will perform tasks as defined for the specified subcommand (e.g. tag). Different set of subcommands might be defined for each VCS and each of them might accept a different set of SUBCOMMAND OPTIONS (see below). All locally unrecognized subcommand options (or the ones specified as EXTERNAL TOOL OPTIONS after --) will be passed to the external VCS tool(s) which pkgkde-vcs executes to do the job. pkgkde-vcs accepts a couple of common options which apply to the helper as whole or are common for all VCSes it supports. They should be passed before subcommand in order to be recognized. Even if pkgkde-vcs does extensive sanity checks before doing anything, an underlying command it executes might still fail. Then pkgkde-vcs will terminate immediately possibly leaving repository in an inconsistent state. It is up to a user to recover from such a failure. At the moment, pkgkde-vcs supports only Git VCS. OPTIONS
Common options -y By default, execution of the first external command that makes changes to the repository has to be explicitly confirmed by user. However, if this option is specified, the first command will be run without confirmation. -n Do not run any external commands that make changes to the repository. Useful with -v to see what commands with what options would be run. -v Be more verbose (e.g. show external commands as they are executed). -- EXTERNAL TOOL OPTIONS Pass additional EXTERNAL TOOL OPTIONS to the external commands pkgkde-vcs executes to accomplish the task. See documentations of the specific subcommand for more details. SUPPORTED VERSION CONTROL SYSTEMS AND SUBCOMMANDS
Git In order to use pkgkde-vcs with Git, git(1) must be available in PATH. Bare Git repositories are not supported and Git repository should be in the fully checked out state (except clone). The following subcommands for Git repositories are supported at the moment: clone Clone the specified pkg-kde git repository. This subcommand should be specified by forcing VCS to git, i.e. by running pkgkde-git command rather than pkgkde-vcs. Repository should be specified relatively to the root of the official pkg-kde repository tree. Once operation is complete, the cloned repository will be put at the same relative location on the local filesystem and update-config (see below) will be executed on it. For example, in order to clone kde4libs repository from kde-sc, akonadi repository from kde-req and pkg-kde-tools repository from the root tree, execute: $ pkgkde-git clone kde-sc/kde4libs $ pkgkde-git clone kde-req/akonadi $ pkgkde-git clone pkg-kde-tools tag Tag current packaging state (HEAD) as upload to Debian archive. Repository working tree must be clean before executing this subcom- mand. Current package version and target distribution are automatically determined from debian/changelog. Distribution must be a valid Debian suite in order to avoid tagging of unfinished (aka UNRELEASED) revisions. The subcommand will create an annotated Git tag under "debian/" namespace. The subcommand itself does not accept any additional options. All EXTERNAL TOOL OPTIONS (if specified) and will be passed to git tag invocation. It is recommended to sign tags by speci- fying -s option. The tag created by pkgkde-vcs tag will meet the following requirements: o The tag will named as "debian/<version>" where <version> is a full debian package version without epoch. All occurrences of the ~ character in <version> will be replaced with the - character because Git does not support ~ character in tag names. o The tag will be assigned the message with content like <version>/<distribution>" where <version> is a full debian version of the package (without any modifications including epoch) and <distribution> is the distribution this package is uploaded. For example, a standard pkgkde-vcs tag will execute the following under the hood (assuming version is 1:2.3.4-5 and distribution is experimental): $ git tag debian/2.3.4-5 -m "1:2.3.4-5/experimental" update-config Do some common configuration on the checked out packaging repository. At the moment, the subcommand performs the following: o Set up master branch and debian tags for pushing. -f option may be specified to force update of the pushing configuration even if some pushing configuration already exists. o Set repository user name and email address to the values of the DEBFULLNAME and DEBEMAIL environment variables respectively. -f option may be specified to override the values even if the repository has some specified already. LICENSE
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. AUTHORS
Modestas Vainius <modax@debian.org> 0.15 2012-05-27 PKGKDE-VCS(1)
All times are GMT -4. The time now is 11:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy