01-15-2008
Yes, that's exactly it.
Do the resize to make sure you are under the capacity of two of the four disks, then the vxassist. I have had to do this recently when someone decided to grow a volume on a systems where the second plex in a mirror was detached and disassociated and a someone else decided to grow the volume and allocated all of the disks is the diskgroup as available. As a result an additional subdisks were allocated on on of the disks that should only have been assigned to the mirror plex.
I'll see if I have a machine handy and I'll a screen dump of this scenario, and the exact sequence.
10 More Discussions You Might Find Interesting
1. Solaris
All solaris rescue gurus out there ....
I've a Solaris 2.6 E450 on which my sysadmin guy has deleted every file (not sub-directories) from the /etc directory.
The machine is (was) running Vxvm with the root volume encapsulated.
I've tried booting from CDROM, mounting the root volume... (3 Replies)
Discussion started by: andy11983
3 Replies
2. AIX
Hi..
I have to resize a partition(filesystem). I mean reduce the size one particular partition and increase the size of another. What should I do?? Pls help
Bala (5 Replies)
Discussion started by: balaji_prk
5 Replies
3. SuSE
Hello Experts,
I am very new to unix environment.
Root filesystem in one of our Linux boxes has almost reached 100%. is there a procedure/ way to resize the root filesystem.
******************************************************
ld8331:/ # df -h|more
Filesystem Size Used... (2 Replies)
Discussion started by: ashok1784
2 Replies
4. UNIX for Dummies Questions & Answers
i am facing a problem, i would like to resize a file system called /pcard04 i am not useing any voulme manager and we have a NETAPP center storge.
what i did is
root@cms-dev # df -h | grep /pcard04
/dev/dsk/c4t60A9800043346C35636F2D6D4F354743d0s0 5.2G 4.0G 1.0G 80% /pcard04
then... (1 Reply)
Discussion started by: q8devilish
1 Replies
5. Solaris
Hi all,
currently , my root filesystem already reach 90 ++%
I already add more cylinder in the root partition as below
Part Tag Flag Cylinders Size Blocks
0 root wm 67 - 5086 38.46GB (5020/0/0) 80646300
1 swap wu 1 - ... (11 Replies)
Discussion started by: SmartAntz
11 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I wanted to find out that in my database server which filesystems are shared storage and which filesystems are local. Like when I use df -k, it shows "filesystem" and "mounted on" but I want to know which one is shared and which one is local.
Please tell me the commands which I can run... (2 Replies)
Discussion started by: kamranjalal
2 Replies
7. Solaris
hi all,
how can we check whether vxvm is installed in our system or not in solaris?
Thanks in advance
dinu (4 Replies)
Discussion started by: dinu
4 Replies
8. Solaris
Hi guys!
Could you tell me what's the difference of filesystem of Solaris to filesystem of Windows? I need to compare both.
I have read some over the net but it's so much technical. Could you explain it in a more simpler term? I am new to Solaris. Hope you help me guys.
Thanks! (4 Replies)
Discussion started by: arah
4 Replies
9. AIX
Dear all,
We are facing prolem when we are going to mount AIX filesystem, the system returned the following error
0506-307The AFopen call failed
: A file or directory in the path name does not exist.
But when we ls filesystems in the /etc/ directory it show
-rw-r--r-- 0 root ... (2 Replies)
Discussion started by: m_raheelahmed
2 Replies
10. Red Hat
Is it possible to resize a filesystem by resizing the LUN on RHEL 6.4 64-bit with LVM and no impact to running applications? The research I have done so far seems to take the approach of adding a new LUN and then expaning the volume group to the new LUN. I'm looking for an approach that avoids a... (7 Replies)
Discussion started by: aenagy
7 Replies
vgchgid(1M) vgchgid(1M)
NAME
vgchgid - modify the Volume Group ID (VGID) on a given set of physical devices
SYNOPSIS
PhysicalVolumePath [PhysicalVolumePath] ...
DESCRIPTION
The command is designed to change the LVM Volume Group ID (VGID) on a supplied set of disks. will work with any type of storage, but it is
primarily targeted at disk arrays that are able to create "snapshots" or "clones" of mirrored LUNs. accepts a set of raw physical devices
and ensures that they all belong to the same volume group, before altering the VGID (see section).
The same VGID is set on all the disks and it should be noted that in cases of multi-PV volume groups, all the physical volumes should be
supplied in a single invocation of the command.
Options
recognizes the following options and arguments:
PhysicalVolumePath The raw devices path name of a physical volume.
Background
Some storage subsystems have a feature which allows a user to split off a set of mirror copies of physical storage (termed or just as LVM
splits off logical volumes with the command. As the result of the "split," the split-off devices will have the same VGID as the original
disks. is needed to modify the VGID on the BCV devices. Once the VGID has been altered, the BCV disks can be imported into a new volume
group by using
WARNINGS
Once the VGID has been changed, the original VGID is lost until a disk device is re-mirrored with the original devices. If is used on a
subset of disk devices (for example, two out of four disk devices), the two groups of disk devices would not be able to be imported into
the same volume group since they have different VGIDs on them. The solution is to re-mirror all four of the disk devices and re-run on all
four BCV devices at the same time, and then use to import them into the same new volume group.
If a disk is newly added to an existing volume group and no subsequent LVM operations has been performed to alter the structures (in other
words, operations which perform an automated vgcfgbackup(1M)); then it is possible a subsequent will fail. It will report that the disk
does not belong to the volume group. This may be overcome by performing a structure changing operation on the volume group (for example,
using
It is the system administrator's responsibility to make sure that the devices provided in the command line are all Business Copy volumes of
the existing standard physical volumes and are in the ready state and writable. Mixing the standard and BC volumes in the same volume
group can cause data corruption.
RETURN VALUE
returns the following values:
0 VGID was modified with no error
1 VGID was not modified
EXAMPLES
An example showing how might be used:
1. The system administrator uses the following commands to create the Business Continuity (BCV or BC) copy:
1) For EMC Symmetrix disks, the commands are and
2) For XP disk array, the commands are and
Three BCV disks are created.
2. Change the VGID on the BCV disks.
3. Make a new volume group using the BCV disks.
This step can be skipped as the group file will be created automatically. If the file is manually created it will have different major
and minor numbers (see lvm(7)).
4. Import the BCV disks into the new volume group.
5. Activate the new volume group.
6. Backup the new volume group's LVM data structure.
7. Mount the associated logical volumes.
SEE ALSO
vgimport(1M), vgscan(1M), vgcfgbackup(1M).
vgchgid(1M)