10 More Discussions You Might Find Interesting
1. Solaris
Hello Admins..
I am going through solaris volume manager guide for RAID-0 concatenation and stripes, I do not understand the concept of stripe from following example of concatenation.
There is an eample for concatenation:
# metainit d25 1 1 c0t1d0s2
d25: Concat/Stripe is setup
the... (5 Replies)
Discussion started by: snchaudhari2
5 Replies
2. 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
3. Solaris
Hi Friends,
I have to migrate my raid-1 volume to raid -5 online.
Can anyone please help me, If possible then send me the step by step commands for online migration.
Thanks in advance. (2 Replies)
Discussion started by: rajaramrnb
2 Replies
4. Solaris
hi all,
i have a doubt. I am doing some R & D in sun volume manager. Sun solaris 5.10 is running in my sun blade 150 sparc machine. I have attached ultrascsi storage box(6x36GB hdd's) with my machine. when i create a raid 0 striping or raid 1 mirroring the output of metastat says Dbase = No. Can... (2 Replies)
Discussion started by: kingston
2 Replies
5. Solaris
hi all
I want to practice on veritas volume manager. Is there any trial version for solaris 5.10 sparc version. If it is there, please give me the link? (1 Reply)
Discussion started by: kingston
1 Replies
6. Solaris
Hello All,
I have small doubt. It's related to SVM in solaris 10. I have created raid 0 (striping) using 3 slices of 500 MB size (default interlace value as 32KB)
d2: Concat/Stripe ---- Interlace value is 32 KB
Size: 2923830 blocks (1.4 GB)
Stripe 0: (interlace: 64 blocks)
Device Start... (1 Reply)
Discussion started by: vaibhav.kanchan
1 Replies
7. 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
8. 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
9. 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
10. AIX
I have a pretty basic question but I am finding my self stumped...
I am trying to find the config that shows which logical volume is mapped to which physical volume
IE:
I know that pdisk15 is mapped to hdisk17 (I only know this as it was told to me though, by IBM)
When I run: lslv -p... (5 Replies)
Discussion started by: pheusion
5 Replies
vxtune(1M) vxtune(1M)
NAME
vxtune - adjust Veritas Volume Replicator and Veritas Volume Manager tunables
SYNOPSIS
vxtune [-r]
vxtune [-r] tunable
vxtune [-r] tunable value
DESCRIPTION
The vxtune utility manages the various memory tunables that are used by Veritas Volume Replicator (VVR). It can also be used to change the
value of the volpagemod_max_memsz tunable that is used by the instant snapshots feature of Veritas Volume Manager (VxVM). No other VxVM
tunables are currently tunable using vxtune.
You can use vxtune to display, set or change the memory tunables that are used by VVR. To maximize VVR performance, you can use this util-
ity to experiment with different values before deciding on the optimal tunable values.
The main advantage of using vxtune to change tunable values is that the new values are available immediately without needing to reboot the
system.
When invoked with no arguments, vxtune displays a list of the tunables whose values may be displayed or set.
When invoked with the name of a supported tunable as the argument, vxtune displays the value of that tunable.
When invoked with the name of a supported tunable and a value as arguments, vxtune attempts to set the tunable to that value.
The specified value can take the following prefixes as base specifiers:
0 Value is in octal.
0x Value is in hexadecimal.
By default, decimal is assumed.
The specified value can take the following suffixes as unit multipliers:
g or G The specified value is in gigabytes.
k or K The specified value is in kilobytes.
m or M The specified value is in megabytes.
By default, the units are assumed to be bytes.
The values of the following memory tunables may be displayed or set:
vol_max_nmpool_sz
Maximum memory that will be used by VVR on a secondary to hold the write requests coming from the primary. This memory is sys-
tem-wide and restricts all secondary RVGs on the system. It may also be useful to increase this tunable if multiple Secondary
RVGs are present on the system.
vol_max_rdback_sz
Maximum memory that will be used by VVR, when write requests are being read back from the SRL. You may need to increase this tun-
able if you have multiple asynchronous RLINKS in one or more RVGs.
vol_max_wrspool_sz
Used in the clustered version of VVR.
vol_min_lowmem_sz
Minimum Threshold of available VVR memory needed to keep the write requests in memory on the primary RVG to send it to secondary.
If available VVR memory is less than this threshold, write requests are freed early so that readbacks can be performed later.
This tunable is used by asynchronous RLINKs.
vol_rvio_maxpool_sz
Maximum memory requested from the system by VVR for internal purposes. This tunable has a direct impact on the performance of VVR
as it prevents one I/O operation from using all the memory in the system. The value of vol_rvio_maxpool_sz must be at least 10
times greater than the value of the maximum I/O size.
volpagemod_max_memsz
Maximum memory, measured in kilobytes, that is allocated for caching FastResync and cache object metadata by the instant snap-
shots feature of VxVM. This tunable has a default value of 6144KB(6MB) of physical memory.
The memory allocated for this cache is exclusively dedicated to it. It is not available for other processes or applications.
Setting the value of volpagemod_max_memsz below 512KB fails if cache objects or volumes that have been prepared for instant snap-
shot operations are present on the system.
If you do not use the FastResync or DRL features that are implemented using a version 20 DCO volume, the value of volpage-
mod_max_memsz can be set to 0. However, if you subsequently decide to enable these features, you can use vxtune to change the
value to a more appropriate one.
OPTIONS
-r (Raw) By default, tunable values are displayed in kilobytes. This option causes values to be displayed in bytes.
EXAMPLES
Display the tunable parameters that vxtune supports:
vxtune
Display the value of vol_min_lowmem_sz on a host:
vxtune vol_min_lowmem_sz
Modify the value of vol_min_lowmem_sz to 2 megabytes on a host:
vxtune vol_min_lowmem_sz 2M
EXIT CODES
The vxtune utility exits with a non-zero status if the attempted operation fails.
A non-zero exit code is not a complete indicator of the problems encountered but denotes the first condition that prevented further execu-
tion of the utility.
NOTES
The vxtune command only affects the tunable values on the host on which it is run. If required, you must run the command separately on each
host for which you want to change the tunable values (for example, for the log-owner node and any of its failover nodes in a cluster).
Values that have been specified using vxtune are persistent across reboots.
SEE ALSO
vrport(1M), vxmemstat(1M), vxsnap(1M)
Veritas Volume Replicator Configuration Notes
Veritas Volume Manager Administrator's Guide
VxVM 5.0.31.1 24 Mar 2008 vxtune(1M)