|
boot=volboot_path
|
|
Specifies the path name to use for the
volboot
file.
This is primarily useful with the
stub
debug option.
The volboot file contains the name of the boot disk group
if the root disk is under VxVM control.
It also contains a host ID that is stored on disks
in imported disk groups to define ownership of disks as a sanity check
for disks that might be accessible from more than one host.
|
cleartempdir
|
|
Removes and recreates the
/etc/vx/tempdb directory.
This directory stores configuration information that
is cleared after system reboots
(or cleared for specific disk groups on import and deport operations).
If the contents of this directory are corrupted,
due to a disk I/O failure for example, vxconfigd will
not start up if it is killed and restarted.
Such a situation can be cleared by starting
vxconfigd
with
-x cleartempdir.
This option has no effect if
vxconfigd
is not started in enabled mode.
|
|
Note: It is advisable to kill any running operational commands
(vxvol, vxsd, or vxmend)
before using the
-x cleartempdir
option.
Failure to do so may cause these commands to fail,
or may cause disastrous but unchecked interactions
between those commands and the issuance of new commands.
It is safe to use this option while running
the graphical user interface,
or while Veritas Volume Manager background daemons are running
(vxsparecheck, vxnotify, or vxrelocd).
|
darecs=darecs_path
|
|
Specifies the pathname to the file that contains persistent
disk access records. This file contains a list of disks that
are scanned and configured by VxVM.
|
devprefix=prefixdir
|
|
Specifies a directory path name to prefix for any disk device accessed by
vxconfigd. For example, with devprefix=/tmp, any access to a
raw disk device named hdisk10 would actually be directed to the
file /tmp/dev/rdsk/hdisk10.
In stubbed mode,
vxconfigd
can operate with such files being regular files.
vxconfigd only requires entries in the prefixdir
/dev
directory in stubbed mode.
See
stub
below for more information.
|
log | nolog
|
|
Logs all
vxconfigd
console output
directly to a file.
This method of logging is very reliable in that any
messages output before a system crash are available in the log file
(if the crash did not corrupt the file system).
You can enable direct
vxconfigd
logging with the
-x log
argument,
and turn it off with the
-x nolog
argument.
Logging is disabled by default.
|
|
If direct logging is enabled,
the default log file is
/var/adm/ras/vxconfigd.log.
This option can be used in conjunction with
syslog | nosyslog.
See
syslog | nosyslog
below for more information.
|
|
The following command
logs all debug and error messages to the specified log file:
|
|
|
logfile=logfilename
|
|
Specifies an alternate
vxconfigd
direct log file.
This option requires using the
-x log
argument.
|
noautoconfig
|
|
vxconfigd
usually configures disk devices
that can be found by inspecting kernel disk drivers automatically.
These
auto_configured
disk devices are not stored in persistent configurations,
but are regenerated from kernel tables after every reboot.
Invoking
vxconfigd
with
-x noautoconfig
prevents the automatic configuration of disk devices,
forcing VxVM to use only those disk devices
configured explicitly using
vxdisk define
or
vxdisk init.
|
nothreads
|
|
Runs
vxconfigd
single-threaded.
|
request_threads=count
|
|
Specifies the number of request handlers that are configured
when vxconfigd is started. The request_threads option
overrides any default values or values set previously with the
vxdctl command. The request_threads option is incompatible
with the -x nothreads option.
|
stub
|
Specifies not to communicate configuration changes to the kernel.
stub
is typically used as a demonstration mode of operation for
vxconfigd.
In most aspects,
a stubbed
vxconfigd
behaves like a regular
vxconfigd,
except that disk devices can be regular files and volume nodes are not created.
A stubbed
vxconfigd
can run concurrently with a regular
vxconfigd,
or concurrently with any other stubbed
vxconfigd
processes,
as long as different rendezvous,
volboot,
and disk files are used for each concurrent process.
|
|
Other Veritas Volume Manager utilities can detect when they are connected to a
vxconfigd
that is running in stubbed mode.
When a VM utility detects a stubbed-mode
vxconfigd,
the utility typically stubs out
any direct use of volumes or plexes itself.
This allows utilities to make configuration changes
in a testing environment that
runs without any communication with the kernel or creation of real
volumes or plexes.
|
syslog | nosyslog
|
|
vxconfigd
supports using the
syslog()
library call to log all of its console messages
(this includes error,
warning,
and notice messages,
but not debug messages).
By default, vxconfigd
redirects console messages to syslog() when it
is first started.
You can disable syslog() logging using the
-x nosyslog argument,
and turn it on with the -x syslog argument.
You can also enable or disable syslog()
logging at boot-time by editing the Veritas Volume Manager startup scripts.
|
|
syslog
can be specified along with
log
(described above)
to obtain more reliable logging.
For example, the following command
logs all debug messages to the specified log file,
and logs all error messages to both the direct log file and the
conslog
file:
|
|
vxconfigd -x9 -x log -x syslog
|
|
|
synctrace
|
|
Flushes tracefile data to disk,
invoking
fsync,
to ensure that the last entry is included in the file
even if the system crashes.
|
tagged=N
|
|
Displays the timestamp (in milliseconds) and elapsed time values of the vxconfigd subsystems that are executed
when vxconfigd starts. The N argument controls the verbosity of the output. 1 is the
lowest level of verbosity, and 8 is the highest. The command also displays the Begin and End messages of each subsystem,
and any quantities that are relevant to that subsystem. For example, the number of LUN paths during device discovery.
Elapsed time values are shown within the End messages and represent the computed elpased time between the Begin and End messages.
Tagged messages can be used to help determine where time is being spect during vxconfigd startup. This is particularly useful in large LUN configurations. The following sample shows a typical output for tagged messages:
|
timestamp | mstimestamp
|
|
Attaches a date and time-of-day timestamp to all messages written by
vxconfigd
to the console.
If
mstimestamp
is used,
a millisecond value is also displayed,
allowing detailed timing of
vxconfigds
operation.
|
tracefile=file
|
|
Logs all possible tracing information to the specified file.
|
|