10 More Discussions You Might Find Interesting
1. Solaris
Hello,
Does anyone know how I can tell what disk are being not being used by a zpool?
For example in Veritas Volume manager, I can run a "vxdisk list" and disks that are marked as "online invalid" are disk that are not used.
I'm looking for a similar command in ZFS which will easily show... (5 Replies)
Discussion started by: robertinoau
5 Replies
2. AIX
Hi,
I have a filesystem that is created on a VG with 12 disks. The FS is striped on these disks. Now I have to add 10 more disks to this volume group to help increase the space of the same FS that is striped. How should I add these disks to the Vg and i need these disks to be added such the FS... (1 Reply)
Discussion started by: aixromeo
1 Replies
3. Filesystems, Disks and Memory
Dear Friends,
I would like know what are FC related disks and how it will be viewed by generic OSes (Unix, Unix like, Windows & etc.)
AFAIK it is viewed by generic OS as SCSI.
Can we have FC related disks as internal storage(physically) of general purpose machine (Server / PC /... (1 Reply)
Discussion started by: Tlogine
1 Replies
4. Solaris
# metastat
d1: Mirror
Submirror 0: d11
State: Okay
Submirror 1: d12
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 14582208 blocks (7.0 GB)
d11: Submirror of d1
State: Okay
Size: 14582208 blocks... (2 Replies)
Discussion started by: Exposure
2 Replies
5. Solaris
Have a V440 server which we need to connect up to a SE6140. Did the zoning on the 3900 brocade silkworm and did mapping from the array to the host manually host initiator did not autodetect the wwn and had to key in manually. probe-scsi-all cannot show the fc disks. What is the problem here? (7 Replies)
Discussion started by: incredible
7 Replies
6. Solaris
I would like to know if I can move the disks from a V240 chassis into a V440 chassis to use the increased resources (CPU & Memory) to boost performance. I know you can move disks between V210/240 chassis's, but I'm not sure if this would work between 240s & 440s. Any help would be much appreciated. (4 Replies)
Discussion started by: Chains
4 Replies
7. Solaris
whats the command to find name of all disks. Is it iostat -En ? (1 Reply)
Discussion started by: vikashtulsiyan
1 Replies
8. AIX
hay
I'm new in the AIX-environment. Right now i'm testing some stuff out. But i can't test the LVM-part which is (to me) very important. I have 2 disks in my testmachine but it seems only 1 is working wel. I'll show you the output below of the disks...
hdisk0 = in good condition
hdisk2 =... (8 Replies)
Discussion started by: kvanelshocht
8 Replies
9. Solaris
What are y'all using to wipe your solaris disks?
I am being question by IT Security, what I am using to wipe disk.
Is anyone using a 3rd party utility?
I have used the format utility in solaris previously.
But they are looking for something commercial that I can use.
Anyone have... (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
10. UNIX for Dummies Questions & Answers
Hi
How do I check how many disks do I have in Solaris & HP-UX?
Also what does this mean
c9t1d5 in /dev/dsk
what is c, t, d etc
cheers (8 Replies)
Discussion started by: g-e-n-o
8 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)