01-07-2002
I had trouble with this in the beginning also.
Volume Manager has to do with managing the disks, raid, striping, plexes, etc....
Veritas Filesystem is just that. Anything that you need to do to manage the data on the disks. Such as mkfs, mount, online resizing and defragmenting. It also gives you control over I/O, caching, and allocation.
Remember:
VM is managing the disks.
Veritas Filesystem is managing the data on the disks.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
? (1 Reply)
Discussion started by: 98_1LE
1 Replies
2. Solaris
Hi all,
I have a problem with vxvm volume which is mirror with two disks. when i am try to increase file system, it is throwing an ERROR: can not allocate 5083938 blocks, ERROR: can not able to run vxassist on this volume.
Please find a sutable solutions.
Thanks and Regards
B. Nageswar... (0 Replies)
Discussion started by: nageswarb
0 Replies
3. UNIX for Advanced & Expert Users
hy guys
I am new at this thread , i have installed sf 5.0 and wanted to encapsulate root disk but when i get to optionn to enter private region i get this error:
Enter desired private region length
(default: 65536) 512
VxVM ERROR V-5-2-338
The encapsulation operation failed with the... (2 Replies)
Discussion started by: charneet
2 Replies
4. Solaris
Hi all,
Anybody know the URLs of veritas volume manager disk problems,volume problems,root disk problems ...etc.
Please share the URL's. i really appreciate for cooperation.
regards
krishna (4 Replies)
Discussion started by: murthy76
4 Replies
5. Solaris
Can somebody kindly help me to determine which one i should choose to better manipulate OS volume.
RAID manager or veritas volume manager?
Any critical differences between those two?
Thanks in advance. (5 Replies)
Discussion started by: beginningDBA
5 Replies
6. Solaris
Can you please let me know the certification code for veritas volume manager in solaris ? Thanks in advance. (2 Replies)
Discussion started by: gowthamakanthan
2 Replies
7. Solaris
Hi All,
recently i had the project.
Got 2 server, one is Mercury, and another is Procyon.
two server was attached to EMC Box and use the Veritas Filesystem.
My question is,
1. Is it possible first remove the filesystem(/u03,/u04) from Veritas in Procyon, no effect on the data? we still... (5 Replies)
Discussion started by: SmartAntz
5 Replies
8. Solaris
Hiii,
Can any one sugge me best practices for resizing a veritas voulume with vxfs file system?
I tried doing this
vxassist -g stg shrinkto stgvol 209715200
VxVM vxassist ERROR V-5-1-7236 Shrinking a FSGEN or RAID5 usage type volume can result in loss of data. It is recommended... (1 Reply)
Discussion started by: anwesh
1 Replies
9. UNIX for Dummies Questions & Answers
I have a machine (5.10 Generic_142900-03 sun4u sparc SUNW,Sun-Fire-V210) that we are upgrading the storage and my task is to mirror what is already on the machine to the new disk. I have the disk, it is labeled and ready but I am not sure of the next steps to mirror the existing diskgroup and... (1 Reply)
Discussion started by: rookieuxixsa
1 Replies
10. UNIX for Beginners Questions & Answers
Hi Experts,
I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system.
#hastatus -sum
-- System State Frozen
A node1 running 0
A node2 running 0
-- Group State
-- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies
lvmpvg(4) Kernel Interfaces Manual lvmpvg(4)
NAME
lvmpvg - LVM physical volume group information file
SYNOPSIS
DESCRIPTION
is an ASCII file that stores the volume-group information for all of the physical volume groups in the system. The information is stored
in a hierarchical format.
First, it starts with a volume group under which multiple physical volume groups can exist. Under each physical volume group, a list of
physical volumes can be specified. There must be at least one physical volume group in each volume group that appears in this file. The
physical-volume-group name must be unique within the corresponding volume group, although it is permissible to use a common physical volume
group name across different volume groups. There can be as many volume groups in this file as there are in the system.
Instead of using the and commands, the administrator can edit this file to create and extend physical volume groups. However, care must be
taken to ensure that all physical volumes to be included in the file have already been defined in their respective volume groups by previ-
ous use of or
The file format has the following structure. and are keywords that introduce the names of the volume group and physical volume group,
respectively.
pv_path
...
pv_path
...
pv_path
...
The variables are defined as follows:
pv_path The block device path name of a physical volume within the volume group.
pvg_name The name of the physical volume group. It must be unique within the volume group.
vg_name The path name of the volume group.
EXAMPLES
The following example shows an file containing two volume groups: the first containing two physical volume groups, each with two physical
volumes defined in it; the second containing three physical volume groups, each with one physical volume defined in it.
SEE ALSO
vgcreate(1M), vgextend(1M), vgreduce(1M), vgremove(1M), intro(7), lvm(7).
lvmpvg(4)