Sponsored Content
Operating Systems AIX hacmp temp storage for tl8sp2 Post 302250998 by itik on Friday 24th of October 2008 06:02:14 PM
Old 10-24-2008
hacmp temp storage for tl8sp2

Hi All,

Is it possible to create a temporary storage on the oraclevg FS for the tl8sp2? My rootvg is getting low on free space, less than 3G.

I'm I going to use System Management (C-SPOC)/HACMP Logical Volume Management/Shared File Systems.

Is that correct? Is that safe?

I want to do the update always on the passive node which it doesn't have the resources. Is that possible? You can see the oraclevg anyways, right.

Thank you for any comments you may add.
 

We Also Found This Discussion For You

1. AIX

HACMP does not start db2 after failover (db2nodes not getting modified by hacmp)

hi, when I do a failover, hacmp always starts db2 but recently it fails to start db2..noticed the issue is db2nodes.cfg is not modified by hacmp and is still showing primary node..manually changed the node name to secondary after which db2 started immediately..unable to figure out why hacmp is... (4 Replies)
Discussion started by: gkr747
4 Replies
vold(1M)                                                  System Administration Commands                                                  vold(1M)

NAME
vold - Volume Management daemon to manage removable media devices SYNOPSIS
/usr/sbin/vold [-n] [-t] [-v] [-f config-file] [-l log-file] [-d root-dir] [-L debug-level] DESCRIPTION
The Volume Management daemon, vold, creates and maintains a file system image rooted at root-dir that contains symbolic names for removable media devices. These devices include CD-ROMs, floppies, DVDs, and USB 1394 devices. The default root-dir is set to /vol if no directory is specified by the -d option. vold reads the /etc/vold.conf configuration file upon startup. If the configuration file is modified later, vold must be told to reread the /etc/vold.conf file. Do this by entering: example# kill -HUP vold_pid To tell vold to clean up and exit, the SIGTERM signal is used: example# kill -TERM vold_pid where vold_pid is the process ID of vold. A disk storage device can not be removed or inserted while vold is active. To remove or insert a removeable mass storage device such as a USB memory stick, first stop the daemon by issuing the command /etc/init.d/volmgt stop. After the device has been removed or inserted, restart the daemon by issuing the command /etc/init.d/volmgt start. OPTIONS
The following options are supported: -n Never writeback. Volume Management updates media labels with unique information if labels are not unique. This flag keeps Volume Management from changing your media. The default setting is FALSE. -t Dump NFS trace information to the log file. The default setting is FALSE. -v Provide lots of status information to the log file. The default setting is FALSE (do not provide status info to log file). -d root-dir Specify an alternate root directory. The default location is /vol. Setting this will also cause other Volume Management utilities to use this as the default root directory. -fconfig-file Specify an alternate configuration file. The default file is /etc/vold.conf. -llog-file Specify an alternate log file. The default log file is /var/adm/vold.log. -Ldebug-level Change the level (verbosity) of debug messages sent to the log file. The range is 0 to 99 where 0 is nothing and 99 is everything. The default level is 0. ENVIRONMENT VARIABLES
vold sets the following environment variables to aid programs which are called when events such as insert, notify, and eject occur: VOLUME_ACTION Event that caused this program to be executed. VOLUME_PATH Pathname of the matched regex from the vold.conf file. VOLUME_DEVICE Device (in /vol/dev) that applies to the media. VOLUME_NAME Name of the volume in question. VOLUME_USER User ID of the user causing the event to occur. VOLUME_SYMNAME Symbolic name of a device containing the volume. VOLUME_MEDIATYPE Name of the type of media (CD-ROM, floppy or rmdisk) FILES
/etc/vold.conf Volume Management daemon configuration file. Directs the Volume Management daemon to control certain devices, and causes events to occur when specific criteria are met. /usr/lib/vold/*.so.1 Shared objects called by Volume Management daemon when certain actions occur. /var/adm/vold.log the default log file location (see the -l option for a description). /vol the default Volume Management root directory. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWvolu | +-----------------------------+-----------------------------+ SEE ALSO
volcancel(1), volcheck(1), volmissing(1), rmmount(1M), rpc.smserverd(1M), rmmount.conf(4), vold.conf(4), attributes(5), volfs(7FS) System Administration Guide: Basic Administration SunOS 5.10 13 Sept 2004 vold(1M)
All times are GMT -4. The time now is 08:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy