Sponsored Content
Top Forums UNIX for Dummies Questions & Answers veritas filesystem and volume manager Post 12783 by Kelam_Magnus on Monday 7th of January 2002 01:34:41 PM
Old 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.


Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to start Veritas volume manager

? (1 Reply)
Discussion started by: 98_1LE
1 Replies

2. Solaris

How to resize mirror volume in veritas volume manager 3.5 on Solaris 9 OE

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

Regarding Veritas Volume manager

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

veritas volume manager links

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

RAID manager or veritas volume manager

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

Veritas volume manager in 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

removing the filesystem from Veritas Volume Manager

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

Veritas volume manager resize

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

VERITAS Volume Manager - mirror a disk/volume

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

How to extend a disk in veritas volume manager in veritas cluster?

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
vxdisksetup(1M) 														   vxdisksetup(1M)

NAME
vxdisksetup, vxdiskunsetup - configure a disk for use with Veritas Volume Manager SYNOPSIS
vxdisksetup [-ifB] disk_address [attribute ...] vxdisksetup [-ifB] disk_address format=hpdisk [attribute ...] vxdisksetup [-if] disk_address format=cdsdisk [attribute ...] /etc/vx/bin/vxdiskunsetup [-C] [-F] disk_address... DESCRIPTION
The vxdisksetup command configures the disk for use by Veritas Volume Manager (VxVM). vxdisksetup is called by the vxdiskadd command as part of initial disk configuration. It is not typically necessary to call this command directly. Note: In release 4.0 of VxVM, the behavior of the vxdisksetup command has been changed so that it only creates auto-configured disks (with a disk access type of auto; see vxdisk(1M)), which can have one of the following formats: cdsdisk The disk is formatted as a CDS disk that is suitable for moving between different operating systems. This is the default format for non-EFI disks (provided that the -i option is used to write the disk header). It is not suitable for boot disks or EFI disks. Note: As the CDS format is applied to the entire disk and is unsuitable for boot disks, options and attributes that relate to partitions, slices or booting are not applicable. The CDS format is also incompatible with EFI disks. hpdisk The disk is formatted to include a private region that VxVM uses to store configuration information. Following the private region, the remainder of the disk forms the public region from which subdisks can be allocated. This format can be applied to disks that can be used to boot the system. If the disk is not initialized as a boot disk, space is reserved on the disk to allow it to be converted to cdsdisk format if required. The hpdisk format is the default for EFI disks. none The disk is unformatted. Note: This value may be displayed, but it cannot be set as a valid format. The vxdiskunsetup command reverses the configuration done by vxdisksetup and makes the specified disks unusable by VxVM. vxdiskunsetup can be applied only to VxVM-initialized disks that are not in use within an imported disk group. The disk_address argument passed to vxdisksetup or to vxdiskunsetup directs the command to the device that corresponds to the disk being operated upon. The address should be provided in the form c#t#d#, which define a controller number (c#), a SCSI target ID (t#), and a SCSI logical unit number (d#). Each number is specified in decimal and can be multiple digits. If the disks are named using the enclosure based naming scheme, the address usually takes the form enclosurename_diskno. The name must reference a valid disk under the /dev/vx/rdmp directory. The vxdiskunsetup command operates by removing the public and private regions that were created by the last invocation of vxdisksetup on the specified disks. After this operation, those disks are converted from the online to the error state state (as displayed by vxdisk list). The /etc/default/vxdisk file can be used to set the default values of the format and privlen attributes for the vxdisk and vxdisksetup com- mands. Values in this file override inbuilt values, and may themselves be overridden by values specified on the command line. For details, see the vxdisk(1M) manual page. Note: When vxdisksetup is executed on an HP IPF (IA64) system, the target disk is either configured or deconfigured as an EFI partitioned disk. The action that is taken depends on whether the -B option is specified, and whether the disk is already formatted as an EFI parti- tioned disk: o If the -B option is specified, and the disk is not already formatted as an EFI disk, the idisk(1M) utility is called to format the disk as an EFI partitioned disk. The partitioning creates an EFI header in the first 1K block, a 100MB partition (or slice) 1, and partition 2 (the HP-UX partition) on the remainder of the disk. If the vxbootsetup(1M) command is subsequently used to configure the disk as a boot disk, partition 1 is populated with an EFI file system, which contains the boot programs that are needed by an HP IPF system, and the HP-UX partition (partition 2) is set up as a logical simple VxVM disk with the same layout as a non-EFI disk. When vxdisksetup has completed setting up an EFI disk, the resulting disk must be addressed using the s2 suffix to select the logical sim- ple VxVM disk. o If the -B option is not specified and the target disk is currently formatted as an EFI partitioned disk, any EFI formatting is destroyed, and the disk is initialized as a non-EFI partitioned disk. OPTIONS
-B Initializes the Veritas Volume Manager private region to begin at block number 2144. This block is designated as the private region offset for a Veritas Volume Manager root disk. Without this option, the private region is initialized to start at the default block number 128. Note: This option is not supported for cdsdisk format disks. -C vxdiskunsetup usually does not operate on disks that appear to be imported by some other host (for example, a host that shares access to the disk). In this case, the -C option can be specified to force de-configuration of the disk, effectively removing the host locks that were detected by vxdiskunsetup. -f Forces a disk to be initialized even if it is a member of a deported disk group. -F By default, the vxdiskunsetup command only operates on online disks. It does not operate on disks that are imported or offline. This option forces an unsetup operation to be performed on such disks. -i Writes a disk header to the disk, initializes the private region of the disk and makes the disk directly usable (as a new disk in a disk group, for example). Note: A disk that is a member of an imported disk group cannot be initialized. The command also fails if the disk is a member of a deported disk group. The -f option can be used to override the latter restriction. ATTRIBUTES
You can specify attributes to affect the layout strategy used by vxdisksetup. CAUTION: Take great care when using these attributes as they can render a disk unusable by VxVM. config Sets up kernel logs or configuration databases on the disk. This attribute has the opposite effect to the noconfig attribute. This is the default behavior if the -i option is specified. Otherwise, the attribute is ignored. noconfig Prevents setting up kernel logs or configuration databases on the disk. The size of the default private region is set to 160 blocks, which is the minimum allowed private region size. noconfig is ignored unless the -i option is specified. noreserve Do not reserve space for conversion to other formats such as cdsdisk. privlen=length Specifies the length of the private region of the disk. The default size of this area is 32MB. The maximum possible size of the private region is 524288 blocks. For cdsdisk format disks, privlen is silently rounded up to the nearest multiple of 8KB if it is not already a multiple of 8KB. privoffset=offset Indicates the sector offset of the private region on the disk. The default value for the private region offset is block number 128 for non-boot disks and block number 2144 for boot disks. For cdsdisk format disks, privoffset is silently rounded up to the nearest multiple of 8KB that is larger than or equal to 128KB if it is not already a multiple of 8KB or if its value is less than 128KB. publen=length Specifies the length of the public region of the disk. This defaults to the size of the disk minus the private area on the disk. For cdsdisk format disks, publen is silently rounded up to the nearest multiple of 8KB if it is not already a multiple of 8KB. puboffset=offset Sets the offset on the disk where the public region starts. By default, this is past the end of the private region. For the hpdisk format, 128 blocks of disk space are reserved at the end of the private region unless this is overridden by the value of puboffset or the -B option is specified. The reserved space allows for later conversion to the cdsdisk format. For cdsdisk format disks, puboffset is silently rounded up to the nearest multiple of 8KB if it is not already a multiple of 8KB. EXAMPLES
To initialize a disk for regular use, enter: /etc/vx/bin/vxdisksetup -i c2t1d0 To initialize a disk for normal use, but set the private region size to 1MB instead of the default size of 32MB, enter: /etc/vx/bin/vxdisksetup -i c2t1d0 privlen=1m Force deconfiguration of a VxVM-initialized disk, c0f4d0: /etc/vx/bin/vxdiskunsetup -C c0t4d0 NOTES
The default private region size increased from 512KB to 1MB in release 3.2, and from 1MB to 32MB in release 5.0. FILES
/etc/default/vxdisk Defaults file used by the vxdisk and vxdisksetup utilities. SEE ALSO
vxcdsconvert(1M), vxdisk(1M), vxdiskadd(1M), vxintro(1M) VxVM 5.0.31.1 24 Mar 2008 vxdisksetup(1M)
All times are GMT -4. The time now is 05:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy