Sponsored Content
Full Discussion: Help with Solaris 8
Operating Systems Solaris Help with Solaris 8 Post 302990149 by phanidhar6039 on Monday 23rd of January 2017 05:36:17 AM
Old 01-23-2017
Quote:
Originally Posted by DukeNuke2
I would say the disk /pci@9,700000/scsi@3,1 is about to die...
None of the disk are on it. At the end it says glm1 and glm2

All my disks are on /pci@8,600000/
 

4 More Discussions You Might Find Interesting

1. Solaris

application compiled on solaris 10 throwing error when executed on solaris 9

I have compiled my application on Solaris 10 with following description SunOS ldg1 5.10 Generic_138888-03 sun4v sparc SUNW,Sun-Blade-T6320 The compiler is Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25 But when installing the application on Solaris 9 SunOS odcarch02 5.9... (2 Replies)
Discussion started by: ash_bit2k2
2 Replies

2. Solaris

Unable to login using ssh,telnet onto my solaris machine with solaris 10 installed

Hi, I am unable to login into my terminal hosting Solaris 10 and get the below error message "Server refused to allocate pty ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory " Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies

3. Solaris

root disk mirroring in solaris volume manager for solaris 10

Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment. Let me know if you need any deatils on this. Thanks, Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies

4. Solaris

Patching Procedure in Solaris 10 with sun cluster having Solaris zone

Hi Gurus I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow. Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies
vxsplitlines(1M)														  vxsplitlines(1M)

NAME
vxsplitlines - show disks with conflicting configuration copies in a cluster SYNOPSIS
vxsplitlines [-g diskgroup] [-c daname] DESCRIPTION
If you import portions of a disk group on different systems, this can lead to conflicting configuration copies on the disks of the disk group. If the configuration information in a disk group is ambiguous, it may not be possible for Veritas Volume Manager to determine which config- uration copy is most up-to-date. (This is usually termed a serial split brain (SSB) condition when it occurs in a cluster.) You cannot import a disk group in this state unless you specify which disk's configuration copy to use. You can use the vxsplitlines command to see which disks in a disk group have conflicting configuration copies, and use this information together with your knowledge of the history of the disk groups' usage to determine which configuration copy is most valid. The output from vxsplitlines displays the vxdg commands that you can run to import the disk group using the available configuration copies. The -o selectcp option of the vxdg import command is used to select the configuration copy to use for the import. OPTIONS
-c daname Display the SSB IDs for each disk that are stored in the configuration copy on the disk specified by its disk access name. Note: Although the SSB IDs for some disks may match, this does not necessarily mean that those disks' configuration copies have recorded all the configuration changes. When viewed from some other configuration copies, the SSB IDs of the same disks may not match. -g diskgroup Specifies the disk group. If a disk group is not specified, the default disk group is used as determined from the rules on the vxdg(1M) manual page. EXAMPLES
Display the disks on each side of the split in the disk group newdg: vxsplitlines -g newdg Display the SSB IDs stored in the configuration copy on disk c2t4d0: vxsplitlines -g newdg -c c2t4d0 NOTES
The vxsplitlines is primarily intended to be used with private disk groups, but it also works with shared disk groups. The version number of the disk group must be 110 or greater. SEE ALSO
vxdg(1M) Veritas Volume Manager Administrator's Guide VxVM 5.0.31.1 24 Mar 2008 vxsplitlines(1M)
All times are GMT -4. The time now is 04:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy