04-04-2013
Unable to varyonvg after copy vg from XIV
Hi all,
I am not sure whether anyone of you using XIV to copy vg from one host to another. After I managed to copy all the respective vg over to destination vg, and map all vg to destination and when come to varyonvg, I got the following error
0516-510 varyonvg: Physical volume not found for physical volume
identifier 00f626989f51fcae.
Anyone encounter this before, hope you can share some idea why it happen and how to resolve this ?
Is this something I didn't perform before I varyonvg ?
Thanks in advance.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello all,
Strange problem on p5 520 server. I've created two volume groups, filesystems, etc.. Everything working fine, without any problem. After some tests with a DS4300 unit I wanted to remove the volume groups, change the DS4300 configuration, and re-create a new volumegroup. However, I'm... (0 Replies)
Discussion started by: EricBE
0 Replies
2. UNIX for Dummies Questions & Answers
I am trying to move a file that is in the root directory. I suspect it is an old file created by someone when the system was installed. I am testing accessing the file by doing a copy but the command does not find the file.
I am operating as root. We are HP-UX B.11.23
I do long listing and... (3 Replies)
Discussion started by: phcorn
3 Replies
3. AIX
Good evening,
Thanks a lot for your help, we appreciate it a bunch. Heres basically a summary of what we have (sorry Im adding some extra history as well):
We have 2 Ibm Servers (Hag and Aki) that are running AIX Version 5. Each connect to a SAN device via 2 separate fiber paths. Hag seems to... (9 Replies)
Discussion started by: aix-olympics
9 Replies
4. AIX
Hi all.
I'm new to AIX, so... We are running a BCV process between two AIX 5 machines attached to EMC Clariion SAN. During the varyonvg portion of the BCV process, we experienced a failure due to the physical volume is marked missing (PVMISSING). What diagnostics can I run to see the missing... (2 Replies)
Discussion started by: KSFlyer
2 Replies
5. AIX
Hello,
On Aix 5.3, during importvg, the varyonvg fails:
importvg -y vgtest hdisk20
0516-013 varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
When i use manually the command varyonvg -u -b -t vgtest to force, the vg can... (3 Replies)
Discussion started by: dantares
3 Replies
6. Solaris
Hi,
I'm learning for my Solaris 10 sys-admin part 2. I'm now trying to get nis working because for the exercise. I run in to a problem.
Setup:
Three Systems
solaris101 (client)
Nothing wrong here havent made any config changes yet.
solaris102 (master server)
Interfaces
... (1 Reply)
Discussion started by: jld
1 Replies
7. Solaris
Hi guys,
I had a solaris box, with veritas controled disk.
1 disc is showing soft errors, how can I repair the soft errors?
Please help.
Cheers; (4 Replies)
Discussion started by: Mujakol
4 Replies
8. Shell Programming and Scripting
I am trying to move content of a folder usingls /backup/db_backups/INCREMENTAL/|while read file ; do
mv $file /backup_LOCAL/db_backups/INCREMENTAL/
done...but when I run this command using a bash script I'm getting this error ./test.sh
mv: cannot stat... (6 Replies)
Discussion started by: rocking77
6 Replies
9. AIX
Iam new to AIX
I am unable varyonvg on the vios,some of the disk are reported as harware failure.
I am going to replace the disk,Please tell me how to remove the disk without any corruption in the VG
lspv -l hdiskx also didn't work (0 Replies)
Discussion started by: roayaix
0 Replies
10. AIX
Hi there,
I am trying to determine if a specific XIV LUN on AIX is in OPEN or CLOSED state. I would like tthe same info as I can get from pcmpath command on v7000 LUN-s. I would need this info to find out if I can safely delete a LUN or not.
I tried fuser command, but no luck. It did not... (6 Replies)
Discussion started by: trifo75
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] [-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, and --maxphysicalvolumes (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.
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.67(2) (2010-06-04) VGSPLIT(8)