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
File::Find::Rule::VCS(3pm)				User Contributed Perl Documentation				File::Find::Rule::VCS(3pm)

NAME
File::Find::Rule::VCS - Exclude files/directories for Version Control Systems SYNOPSIS
use File::Find::Rule (); use File::Find::Rule::VCS (); # Find all files smaller than 10k, ignoring version control files my @files = File::Find::Rule->ignore_vcs ->file ->size('<10Ki') ->in( $dir ); DESCRIPTION
Many tools need to be equally useful both on ordinary files, and on code that has been checked out from revision control systems. File::Find::Rule::VCS provides quick and convenient methods to exclude the version control directories of several major Version Control Systems (currently CVS, subversion, and Bazaar). File::Find::Rule::VCS implements methods to ignore the following: CVS Subversion Bazaar In addition, the following version control systems do not create directories in the checkout and do not require the use of any ignore methods SVK Git METHODS
ignore_vcs # Ignore all common version control systems $find->ignore_vcs; # Ignore a specific named version control systems $find->ignore_vcs($name); # Ignore nothing (silent pass-through) $find->ignore_vcs(''); The "ignore_vcs" method excludes the files for a named Version Control System from your File::Find::Rule search. If passed, the name of the version control system is case in-sensitive. Names currently supported are 'cvs', 'svn', 'subversion', 'bzr', and 'bazaar'. As a convenience for high-level APIs, if the VCS name is the defined null string '' then the call will be treated as a nullop. If no params at all are passed, this method will ignore all supported version control systems. If ignoring every version control system, please note that any legitimate directories called "CVS" or files starting with .# will be ignored, which is not always desirable. In widely-distributed code, you instead should try to detect the specific version control system used and call ignore_vcs with the specific name. Passing "undef", or an unsupported name, will throw an exception. ignore_cvs The "ignore_cvs" method excluding all CVS directories from your File::Find::Rule search. It will also exclude all the files left around by CVS after an automated merge that start with '.#' (dot-hash). ignore_rcs The "ignore_rcs" method excluding all RCS directories from your File::Find::Rule search. It will also exclude all the files used by RCS to store the revisions (end with ',v'). ignore_svn The "ignore_svn" method excluding all Subversion (".svn") directories from your File::Find::Rule search. ignore_bzr The "ignore_bzr" method excluding all Bazaar (".bzr") directories from your File::Find::Rule search. ignore_git The "ignore_git" method excluding all Git (".git") directories from your File::Find::Rule search. ignore_hg The "ignore_hg" method excluding all Mercurial/Hg (".hg") directories from your File::Find::Rule search. TO DO
- Add support for other version control systems. - Add other useful VCS-related methods SUPPORT
Bugs should always be submitted via the CPAN bug tracker <http://rt.cpan.org/NoAuth/ReportBug.html?Queue=File-Find-Rule-VCS> For other issues, contact the maintainer AUTHOR
Adam Kennedy <adamk@cpan.org> SEE ALSO
<http://ali.as/>, File::Find::Rule COPYRIGHT
Copyright 2005 - 2010 Adam Kennedy. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of the license can be found in the LICENSE file included with this module. perl v5.10.1 2010-10-06 File::Find::Rule::VCS(3pm)
All times are GMT -4. The time now is 10:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy