10 More Discussions You Might Find Interesting
1. HP-UX
Scenario1:
VG00 lvm,not mirrored,2 disk of 36GB vg size
VG00 size is under 30G.
Is possible to remove a disk of 36GB and replace "on fly"
with a disk of 300GB on VG00?
Thanks (6 Replies)
Discussion started by: Linusolaradm1
6 Replies
2. AIX
Hi,
I need to know who can I create an script in order to check server mirror in AIX. I got this script
!/usr/bin/ksh
#
# Check if a VG is mirrored.
#
# lsattr -El <lvname> -a strictness -a copies
# If copies=2 and scrictness=y, then VG is mirrored
#
# LVs are retrieved via 'lsvg -l... (5 Replies)
Discussion started by: fede_mont
5 Replies
3. HP-UX
what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 Replies
4. Solaris
Hi,
Can you help me on booting x86 server configured under VxVM. Server boots fine normally from both the disks but if I try to boot server from mirror disk without starting veritas, then it does not boot.
vxplex -g rootdg dis var-02
vxplex -g rootdg dis swapvol-02
vxplex -g rootdg dis... (2 Replies)
Discussion started by: milindphanse604
2 Replies
5. UNIX for Advanced & Expert Users
I apologize is this isn't an appropriate post for the 'advanced' UNIX, so please let me know if I should post this under UNIX for dummies, but here's my problem in a nutshell: I having problems creating a mirrored logical volume.
I have created two new physical volumes
... (2 Replies)
Discussion started by: simonrodan
2 Replies
6. Solaris
I’m setting up a boot disk mirror on Solaris 10 x86. I’m used to doing it on SPARC, where you can copy the partition table using fmthard. My x86 boot disk has 2 primary partitions, a Solaris one and a diagnostic one. Is there a way to copy those 2 primary partitions to the second disk without... (6 Replies)
Discussion started by: TKD
6 Replies
7. Linux
Hi Guys,
I have a mirrored LVM volume, and wish to break the mirror leaving only copy1 (effectively removing copy 0).
Here's the config:
# lvs -a -o +devices
lvdata vg01 mwi-ao 2.19T lvdata_mlog 100.00 lvdata_mimage_0(0),lvdata_mimage_1(0)
vg01... (0 Replies)
Discussion started by: badoshi
0 Replies
8. Ubuntu
Hi,
I have an Ubuntu system which I have an faulted mirror.
I trying to replace the disk, but I'm stuck on that it boots and only showing GRUB
GRUB
## ## End Default Options ##
title Ubuntu 8.04.4 LTS, kernel 2.6.24-26-server
root (hd0,0)
kernel ... (0 Replies)
Discussion started by: jld
0 Replies
9. Solaris
Hi All,
How do you know if you need to break the mirror on solaris 8 patch update?
Here's the patch example, 117350-54. On the site, it's just a low type update and not a medium or critical.
Is breaking a mirror a best practice only or really a requirement to some patch?
Thanks,
itik (1 Reply)
Discussion started by: itik
1 Replies
10. HP-UX
How do we remove mirror (vg00) in itanium system having 11.23 version. (2 Replies)
Discussion started by: jeelans
2 Replies
SVK::Command::Patch(3) User Contributed Perl Documentation SVK::Command::Patch(3)
NAME
SVK::Command::Patch - Manage patches
SYNOPSIS
patch --ls [--list]
patch --cat [--view] PATCHNAME
patch --regen [--regenerate] PATCHNAME
patch --up [--update] PATCHNAME
patch --apply PATCHNAME [DEPOTPATH | PATH] [-- MERGEOPTIONS]
patch --rm [--delete] PATCHNAME
OPTIONS
--depot DEPOTNAME : operate on a depot other than the default one
DESCRIPTION
To create a patch, use "commit -P" or "smerge -P". To import a patch that's sent to you by someone else, just drop it into the "patch"
directory in your local svk repository. (That's usually "~/.svk/".)
svk patches are compatible with GNU patch. Extra svk-specific metadata is stored in an encoded chunk at the end of the file.
A patch name of "-" refers to the standard input and output.
INTRODUCTION
"svk patch" command can help out on the situation where you want to maintain your patchset to a given project. It is used under the
situation that you have no direct write access to remote repository, thus "svk push" cannot be used.
Suppose you mirror project "foo" to "//mirror/foo", create a local copy on "//local/foo", and check out to "~/dev/foo". After you've done
some work, you type:
svk commit -m "Add my new feature"
to commit changes from "~/dev/foo" to "//local/foo". If you have commit access to the upstream repository, you can submit your changes
directly like this:
svk push //local/foo
Sometimes, it's useful to send a patch, rather than submit changes directly, either because you don't have permission to commit to the
upstream repository or because you don't think your changes are ready to be committed.
To create a patch containing the differences between "//local/foo" and "//mirror/foo", use this command:
svk push -P Foo //local/foo
The "-P" flag tells svk that you want to create a patch rather than push the changes to the upstream repository. "-P" takes a single flag:
a patch name. It probably makes sense to name it after the feature implemented or bug fixed by the patch. Patch files you generate will be
created in the "patch" subdirectory of your local svk repository.
Over time, other developers will make changes to project "foo". From time to time, you may need to update your patch so that it still
applies cleanly.
First, make sure your local branch is up to date with any changes made upstream:
svk pull //local/foo
Next, update your patch so that it will apply cleanly to the newest version of the upstream repository:
svk patch --update Foo
Finally, regenerate your patch to include other changes you've made on your local branch since you created or last regenerated the patch:
svk patch --regen Foo
To get a list of all patches your svk knows about, run:
svk patch --list
To see the current version of a specific patch, run:
svk patch --view Foo
When you're done with a patch and don't want it hanging around anymore, run:
svk patch --delete Foo
To apply a patch to the repository that someone else has sent you, run:
svk patch --apply - < contributed_feature.patch
perl v5.10.0 2008-08-04 SVK::Command::Patch(3)