05-21-2008
I have sued both! The trick is to use 'metareplace' in case the entire disk goes bad!! That is faster and works okay
If only some slices are bad, then you need to follow the 'tedious' procedure that you mentioned in the very first post.
Extra:
Concerning usuing the cfgadm command, I have seen most sun engineers not using them while many sys admins use that - may be for security / satisfaction sake. Remember, cfgadm will eb used if you have scsi disks on your machine. ** 'luxadm' command is used instead of cfgadm incase your machine has fiber channel disks. (To find out if your system has FCAL disks, run format command and see if there is a long series of numbers after t (target) of the disks).
Hope that helps
10 More Discussions You Might Find Interesting
1. Solaris
I dont even know what raid level this is, but its raid 5 mirrored from the looks of it.
I have a failed disk (t12) within this mirror. What is the best way to replace this disk? 2 things concern me, isn't there a command to prepare the disk for a hot swap? and what should i do with the... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
2. Solaris
Hi All,
I have to remove the disk from SVM.
Kindly guide me or suggest me some link where in I can steps to remove SVM from Solaris 10 .Also I have one metaset which require deletion.
Thanks in anticipation! (10 Replies)
Discussion started by: kumarmani
10 Replies
3. Solaris
Hi Gurus, I've got an issue here:
(1) Hardware: Sun NetraT1, (2) OS: Solaris 10, (3) SVM
metastat shows /var having 12 GB. df shows /var having 4 GB. Real space for /var is about 4 GB since I can't move a big file to it. How is 8 GB space missing? Does /var/run swap need to account? Can I... (5 Replies)
Discussion started by: aixlover
5 Replies
4. Solaris
Dear All,
Please help me to configure root mirroring using SVM in Solaris 9.
Thanks and Regards,
Lakkireddy BR (3 Replies)
Discussion started by: lbreddy
3 Replies
5. Solaris
The following is the summarry:-
1) Four disks in server ie (c1t0d0. c1t1d0, c1t2d0, c1t3d0). c1t2d0 is the disk to be replaced.
c1t0d0 and c1t2d0 are mirrors.
c1t1d0 and c1t3d0 are mirrors.
Metadb to be deleted is in c1t2d0s7
a) Mirror d35 has 2 submirrors d38 and d39
d38 is a stripe... (0 Replies)
Discussion started by: aji1729
0 Replies
6. Solaris
I tried doing rootdisk mirroring in my local host , i added a new Ide disk in my system
and copied the prtvtoc from root disk to the newly added disk, and then when i tried to add database replicas on both the disks, it was added for boot disk but for the newly added disk i gave the error, which... (6 Replies)
Discussion started by: Laxxi
6 Replies
7. Solaris
Hi All
BAsed on the below I would like to verifu two things
(1) The udnerlying mirroris for '/mnt' na dit onlcy contaisne 1 sub-mirror, with one sliceon is one disk and hence, data loss on the mount point (the mount point, '/mnt' is backed up)
(2) the Procedure for renewal
# df -kh /mnt... (2 Replies)
Discussion started by: stevie_velvet
2 Replies
8. Solaris
Hi
Please can you help me on replacing or removing a faulty disk drive on a SUN NETRA X4250server with 4 internal drives only.
the format comand show me the following:
format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <drive type unknown>
... (9 Replies)
Discussion started by: fretagi
9 Replies
9. Filesystems, Disks and Memory
Hello,
On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active.
We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED.
... (1 Reply)
Discussion started by: terrya
1 Replies
10. AIX
Hello,
On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active.
We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED.
... (3 Replies)
Discussion started by: terrya
3 Replies
LEARN ABOUT HPUX
vxsplitlines
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)