06-12-2009
moved to a more appropriate group...
10 More Discussions You Might Find Interesting
1. Solaris
We have 4 CPU in V880 server. we need to upgrade by one or two CPUs .
Is it possible on 5 or 6 CPU on V880 (3 Replies)
Discussion started by: hdk2oo5
3 Replies
2. Solaris
Hi
how would i upgrade any package from (say) version 4.1 to version 4.2 ?
Help needed and help appreciated
Thanks
chakri (3 Replies)
Discussion started by: chakri.penguin
3 Replies
3. Solaris
Currently we are using Oracle9i Enterprise Edition Release 9.2.0.4.0 in sun solaris 5.9 server.
We wnt to upgrade the oracle database to 10.2g.
My doubt is that " what are the implications of this database upgradation in sun solaris server"
"whether we need to upgrade the sunsolaris 5.9... (3 Replies)
Discussion started by: vamshikrishnab
3 Replies
4. Linux
Hi,
I am not able to upgrade the Linux kernel version 2.6.21.5 to 2.6.25. I tried applying the patches available in the Linux site. The patches are not getting applied successfully. I have the linux kernel 2.6.21.5 with some samsung patches on top of it. I want to upgrade that kernel to 2.6.25... (5 Replies)
Discussion started by: poojasreejith
5 Replies
5. Red Hat
Hi All,
I have some problem in upgrading Linux from kernel 2.4.21-4.EL to 2.4.21-27.EL.
I downloaded the package from
Rpm source :
kernel-source-2.4.21-27.EL.i386 RPM
I upgraded using
rpm -Uvh kernel-source-2.4.21-27.EL
It installed sucessfully, But when i check grub.conf file... (3 Replies)
Discussion started by: VNK
3 Replies
6. Solaris
Hi,
Can anybody help me to upgrade my machinne from solaris 8 to solaris 10
Regards,
ravich (1 Reply)
Discussion started by: ravich
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have UNIX system on which Perl is already installed. When I run the command perl -v
. It gives the output as
This is perl, v5.8.8 built for x86_64-linux-thread-multi
Copyright 1987-2006, Larry Wall
I wanted to upgrade it to the latest version. So, I downloaded the perl onto my... (2 Replies)
Discussion started by: donisback
2 Replies
8. Solaris
Hi All ,
My current Bind version is BIND 9.6.1 and I want upgrade the same to BIND 9.8.1-P1 ,Can any one provide the steps to do the same ?
Solaris Version : 5.10 Generic_144488-11 sun4v sparc
Thanks , (0 Replies)
Discussion started by: sandeep.tk
0 Replies
9. AIX
Using nimadm:
nimadm -j nimadmvg -c sap024 -s spot_6100 -l lpp_6100 -d "hdisk1" -Y
Initializing the NIM master.
Initializing NIM client sap024.
0505-205 nimadm: The level of bos.alt_disk_install.rte installed in SPOT
spot_6100 (6.1.3.4) does not match the NIM master's level (7.1.1.2).... (2 Replies)
Discussion started by: sciacca75
2 Replies
10. AIX
Hi Experts,
I have an AIX machine oslevel -s 5300-00-00
Now I need to upgrade its TL to a level 5300-06-03-0732
Kindly let me know if we can do this directly. I guss we have to upgrade TL from 1 , 2 ,3 ,4, 5 and 6, then I have to upgrade to 06-03-0732 .
Am i right here ? (6 Replies)
Discussion started by: jayadeava
6 Replies
VGSPLIT(8) System Manager's Manual VGSPLIT(8)
NAME
vgsplit - split a volume group into two
SYNOPSIS
vgsplit [--alloc AllocationPolicy] [-A|--autobackup {y|n}] [-c|--clustered {y|n}] [-d|--debug] [-h|--help] [-l|--maxlogicalvolumes MaxLogi-
calVolumes] [-M|--metadatatype type] [-p|--maxphysicalvolumes MaxPhysicalVolumes] [--[vg]metadatacopies] NumberOfCopies|unmanaged|all]
[-n|--name LogicalVolumeName] [-t|--test] [-v|--verbose] SourceVolumeGroupName DestinationVolumeGroupName [ PhysicalVolumePath ...]
DESCRIPTION
vgsplit moves one or more physical volumes from SourceVolumeGroupName into DestinationVolumeGroupName. The physical volumes moved can be
specified either explicitly via PhysicalVolumePath, or implicitly by -n LogicalVolumeName, in which case only physical volumes underlying
the specified logical volume will be moved.
If DestinationVolumeGroupName does not exist, a new volume group will be created. The default attributes for the new volume group can be
specified with --alloc, --clustered, --maxlogicalvolumes, --metadatatype, --maxphysicalvolumes and --[vg]metadatacopies, (see vgcreate(8)
for a description of these options). If any of these options are not given, default attribute(s) are taken from SourceVolumeGroupName. If
a non-LVM2 metadata type (e.g. lvm1) is being used, you should use the -M option to specify the metadata type directly.
If DestinationVolumeGroupName does exist, it will be checked for compatibility with SourceVolumeGroupName before the physical volumes are
moved. Specifying any of the above default volume group attributes with an existing destination volume group is an error, and no split will
occur.
Logical volumes cannot be split between volume groups. Vgsplit(8) only moves complete physical volumes: To move part of a physical volume,
use pvmove(8). Each existing logical volume must be entirely on the physical volumes forming either the source or the destination volume
group. For this reason, vgsplit(8) may fail with an error if a split would result in a logical volume being split across volume groups.
A vgsplit into an existing volume group retains the existing volume group's value of vgmetadatacopies (see vgcreate and lvm.conf for fur-
ther explanation of vgmetadatacopies). To change the value of vgmetadatacopies, use vgchange.
OPTIONS
See lvm for common options.
SEE ALSO
lvm(8), vgcreate(8), vgextend(8), vgreduce(8), vgmerge(8)
Sistina Software UK LVM TOOLS 2.02.95(2) (2012-03-06) VGSPLIT(8)