05-06-2011
Everything is clear now.
Under CAM, map initiators to hosts, and map hosts to volumes. The so-call host is just a name to connect initiators (FC ports) to the disk volumes.
initiators <> hosts <> volumes
Thanks everyone again!
5 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi,
We have 12x1TB SATA disks in our array and I need to create 10TB volume. I defined new storage profile on array and when I tried to add volume, I faced with ~2TB limit for new volumes. I didn't find how to set another limit on my storage profile. Is there is a way to configure one large... (3 Replies)
Discussion started by: Sapfeer
3 Replies
2. Solaris
Hello,
Wondering if anyone can help me with mounting a file share from my Sun T2000 server running Solaris 10 to my connected 2530 disk array?
I believe I've connected the disk array correctly and I have created a volume on the array using the filesystem (Sun_SAM-FS, RAID-5).
The T2000... (15 Replies)
Discussion started by: DundeeDancer
15 Replies
3. Solaris
Hi!
I have Sun StorageTek 2540 FC array and CAM works very slowly - I can wait for software response even more than 2 minutes... I run this software on Windows machine with Firefox Web Browser but speed is terrible... How can I make it works at least a little bit faster?.. (2 Replies)
Discussion started by: Sapfeer
2 Replies
4. Filesystems, Disks and Memory
In Sun manuals, I didn't find how to backup Sun StorageTek Common Array Manager's configuration. Is there a way to do it like backing up Brocade switch configuration? CAM is under Solaris 10.
Thank you in advance! (0 Replies)
Discussion started by: aixlover
0 Replies
5. Solaris
Bought a Sun StorageTek 2540 SAN array a few years ago from a company that was going out of business. When we first set it up, we were able to get all the software (Common Array Manager) and firmware directly from Sun.
We just upgraded the drives, but the array is too large for the firmware. Now... (6 Replies)
Discussion started by: edison303
6 Replies
LEARN ABOUT DEBIAN
vgreduce
VGREDUCE(8) System Manager's Manual VGREDUCE(8)
NAME
vgreduce - reduce a volume group
SYNOPSIS
vgreduce [-a|--all] [-A|--autobackup y|n] [-d|--debug] [-h|-?|--help] [--removemissing] [-t|--test] [-v|--verbose] VolumeGroupName [Physi-
calVolumePath...]
DESCRIPTION
vgreduce allows you to remove one or more unused physical volumes from a volume group.
OPTIONS
See lvm for common options.
-a, --all
Removes all empty physical volumes if none are given on command line.
--removemissing
Removes all missing physical volumes from the volume group, if there are no logical volumes allocated on those. This resumes normal
operation of the volume group (new logical volumes may again be created, changed and so on).
If this is not possible (there are logical volumes referencing the missing physical volumes) and you cannot or do not want to remove
them manually, you can run this option with --force to have vgreduce remove any partial LVs.
Any logical volumes and dependent snapshots that were partly on the missing disks get removed completely. This includes those parts
that lie on disks that are still present.
If your logical volumes spanned several disks including the ones that are lost, you might want to try to salvage data first by acti-
vating your logical volumes with --partial as described in lvm (8).
SEE ALSO
lvm(8), vgextend(8)
Sistina Software UK LVM TOOLS 2.02.95(2) (2012-03-06) VGREDUCE(8)