Sponsored Content
Operating Systems Solaris vxvm root disk booting problem - solved with boot -a. How? Post 302399386 by incredible on Saturday 27th of February 2010 05:42:52 PM
Old 02-27-2010
What is your Veritas Foundation version? Your Solaris OS version?
What caused the system to go down? What were you doing on the system? Any activities during the time? System running any HA?
 

10 More Discussions You Might Find Interesting

1. SCO

sco openserver 5.0.0 boot / root disk

Hi, I have an openserver 5.0.0 machine in the office. The sysad of that machine left years ago without leaving the password to anyone. I was wondering if someone has a copy of the boot / root diskettes (rescue) for this version? Or perhaps if anyone knows a download link / location in the... (0 Replies)
Discussion started by: marcpascual
0 Replies

2. Solaris

Migrate VxVM boot disks to higher capacity disk

Hi, Im getting a downtime of 4 hrs to do porting of bootdisks. Currently, the system is running on Sf4800. 2 internal disk 36G connected to a SE3510 storage. We're getting 72G disks and we want to restore the OS from the current 36G to the 72G disk. System is under veritas volume manager ctrl.... (4 Replies)
Discussion started by: incredible
4 Replies

3. Solaris

( VxVM ) How to add the removed disk back to previous disk group

Previously , i remove the disk by #vxdg -g testdg -k rmdisk testdg02 But i got error when i -k adddisk bash-2.03# vxdisk list DEVICE TYPE DISK GROUP STATUS c0t0d0s2 auto:none - - online invalid c0t1d0s2 auto:none ... (1 Reply)
Discussion started by: waibabe
1 Replies

4. Solaris

Problem by cloning boot disk.

Hello guys! I use the Solaris 10 x86 machine. I need to clone the boot disk. Why, when I copy slice 1 - there is a following: # ufsdump 0f - /dev/rdsk/c0d0s1 | (cd /mnt && ufsrestore rf - ) DUMP: Warning - super-block on device `/dev/rdsk/c0d01` is corrupt - run fsck Dump: The Entire... (6 Replies)
Discussion started by: wolfgang
6 Replies

5. Solaris

Lost Root Password on VXVM Encapsulated Root Disk

Hi All Hope it's okay to post on this sub-forum, couldn't find a better place I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies

6. Solaris

Unable to boot from mirror disk on x86 server configured under VxVM

Hi, Can you help me on booting x86 server configured under VxVM. Server boots fine normally from both the disks but if I try to boot server from mirror disk without starting veritas, then it does not boot. vxplex -g rootdg dis var-02 vxplex -g rootdg dis swapvol-02 vxplex -g rootdg dis... (2 Replies)
Discussion started by: milindphanse604
2 Replies

7. Solaris

Solved: Disk Unable to Boot

Update: The / file system (/dev/rdsk/c1t0d0s0) is being checked fsck unable to stat WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0). Root password for system maintenance (control-d to bypass): I am unable to hit control-d to by pass. I... (50 Replies)
Discussion started by: br1an
50 Replies

8. Red Hat

Booting 2nd mirrored boot disk

Hi guys, thanks for helping out. If you have two boot disk mirrored and your primary boot disk fails, how will you boot the system from the second disk? Thank you very much for your assistance on this matter. Arrey (5 Replies)
Discussion started by: cjashu
5 Replies

9. UNIX for Dummies Questions & Answers

[Solved] Boot Failure - Openindiana w/ Napp-it - Full Root?

Came home the other day to a Napp-it Gui that would not load. Login would appear but when i attempted I would get the following Set default permissions and reading disk and pool parameter, please wait.. in case of problems, try a reboot after Power-Off or check disk and pool status at CLI.... (1 Reply)
Discussion started by: fastedd27
1 Replies

10. HP-UX

Removing a VxVM disk from a Disk Group

Hello all, So I made a rookie mistake today. I forgot to remove my disk from my disk group, before running the following command:for i in `ioscan -fnN | awk /NO/'{print $3}'` do rmsf -H $i done I am trying to run the following command, but not having any luck obviously:vxdg -g dgvol1 rmdisk... (0 Replies)
Discussion started by: mrkejames2
0 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)
All times are GMT -4. The time now is 05:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy