Sponsored Content
Full Discussion: Root Mirroring
Operating Systems AIX Root Mirroring Post 302869405 by aixvinnie on Wednesday 30th of October 2013 08:17:43 AM
Old 10-30-2013
Hi,

is this EMC storage that you are using? If so, did you make sure you enable load balancing and failover functionality on the bootdevice by using the pprootdev tool which is provided by EMC? This tool enables bosboot to work correctly with the powerpath software. The information about the pprootdev tool can be found at the powerpath manual provided by EMC.

Hope this helps,

Vincent
 

9 More Discussions You Might Find Interesting

1. Solaris

Solaris mirroring / non-root disk

Hi Guys, Need to add 2 disks into a JBOD array (3310). Does anyone see anything wrong with my Procedure / Doco below? 1> Logon to system, check system logs for abnormal entries. 2> Make backups of related system files: A>cp -p /etc/system /etc/system.backup.081505 B>cp -p /etc/vfstab... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies

2. Solaris

Veritas root disk mirroring

Hi there, My task is to replace the two 73 G disks with two 143 G disks , which has vxvm 4.1 running on it. I would like to know whether the steps iam following are correct. 1. Break the sub-disks, plexes of the root mirror. 2. Remove the sub-disks,plexes of the root mirror. 3. Remove one of... (10 Replies)
Discussion started by: Jartan
10 Replies

3. Solaris

Unable to boot after an error in mirroring root

Hey Guys, I am using a Sun sparc server and had 6 disks. The root was loaded on c0t10d0s0 disk. I made an image or mirrored the root to another disk c0t9d0s0. But during the process instead of attaching submirrors to main mirror (d0 <--- d01 and d11) i attached d0 <--- d01 and... (1 Reply)
Discussion started by: rjcool
1 Replies

4. Solaris

mirroring root disk using svm - but no free slices for metadb's

Hi all, we have an existing system that was configured using just one of the (two) internal disks. I want to mirror the disk using SVM, but have realised there is no free slice for creating the metadb's. Is there a workaround I can use for this? In the past we have always kept slice 7 free -... (8 Replies)
Discussion started by: badoshi
8 Replies

5. Solaris

Root Disk mirroring in SVM

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

6. Solaris

Disk mismatch while trying to zfs mirroring non-root disks

Hello All, I am trying to mirror two non-root hard drives using zfs. But "fmthard" fails when I try to copy the vtoc due to disk mismatch. Please help me. --- iostat command shows the disk to be similiar --- format command shows disk to be different :confused: --- c1t2d0 is the active... (8 Replies)
Discussion started by: pingmeback
8 Replies

7. SuSE

Root mirroring in SUSE 10.1

Hi, I want to mirror root hard disk in SUSE LINUX 10.1. I have two 80G hard disks, I searched in google but I did not find any good link to describe this. Please see below info.. Server1:~ # df -h Filesystem Size Used Avail Use% Mounted on /dev/sda6 16G... (10 Replies)
Discussion started by: sri243
10 Replies

8. Solaris

Root disk mirroring in SVM

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

9. Solaris

Root disk mirroring in Solaris 10

I would like to perform root disk mirroring task. Can someone please help me out on this. Thanks !! Regards, Rama (2 Replies)
Discussion started by: ramagore85
2 Replies
GIT-MERGETOOL(1)						    Git Manual							  GIT-MERGETOOL(1)

NAME
git-mergetool - Run merge conflict resolution tools to resolve merge conflicts SYNOPSIS
git mergetool [--tool=<tool>] [-y|--no-prompt|--prompt] [<file>]... DESCRIPTION
Use git mergetool to run one of several merge utilities to resolve merge conflicts. It is typically run after git merge. If one or more <file> parameters are given, the merge tool program will be run to resolve differences on each file. If no <file> names are specified, git mergetool will run the merge tool program on every file with merge conflicts. OPTIONS
-t <tool>, --tool=<tool> Use the merge resolution program specified by <tool>. Valid merge tools are: kdiff3, tkdiff, meld, xxdiff, emerge, vimdiff, gvimdiff, ecmerge, diffuse, tortoisemerge, opendiff, p4merge and araxis. If a merge resolution program is not specified, git mergetool will use the configuration variable merge.tool. If the configuration variable merge.tool is not set, git mergetool will pick a suitable default. You can explicitly provide a full path to the tool by setting the configuration variable mergetool.<tool>.path. For example, you can configure the absolute path to kdiff3 by setting mergetool.kdiff3.path. Otherwise, git mergetool assumes the tool is available in PATH. Instead of running one of the known merge tool programs, git mergetool can be customized to run an alternative program by specifying the command line to invoke in a configuration variable mergetool.<tool>.cmd. When git mergetool is invoked with this tool (either through the -t or --tool option or the merge.tool configuration variable) the configured command line will be invoked with $BASE set to the name of a temporary file containing the common base for the merge, if available; $LOCAL set to the name of a temporary file containing the contents of the file on the current branch; $REMOTE set to the name of a temporary file containing the contents of the file to be merged, and $MERGED set to the name of the file to which the merge tool should write the result of the merge resolution. If the custom merge tool correctly indicates the success of a merge resolution with its exit code, then the configuration variable mergetool.<tool>.trustExitCode can be set to true. Otherwise, git mergetool will prompt the user to indicate the success of the resolution after the custom tool has exited. -y, --no-prompt Don't prompt before each invocation of the merge resolution program. --prompt Prompt before each invocation of the merge resolution program. This is the default behaviour; the option is provided to override any configuration settings. AUTHOR
Written by Theodore Y Ts'o <tytso@mit.edu[1]> DOCUMENTATION
Documentation by Theodore Y Ts'o. GIT
Part of the git(1) suite NOTES
1. tytso@mit.edu mailto:tytso@mit.edu Git 1.7.1 07/05/2010 GIT-MERGETOOL(1)
All times are GMT -4. The time now is 09:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy