9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I don't know if I am asking this correctly, but I have a hard drive with some bad sectors and it appears that some of the data is corrupt. I am having allot of trouble copying the data to a new drive. The issue is not in copying files, but that the new drive to which files are copied is not acting... (17 Replies)
Discussion started by: LMHmedchem
17 Replies
2. HP-UX
Hallo Friends,
I have application X running on hpux 11.11 and oracle 9i release 2. I recently had a hardware failure on disk /dev/dsk/c2t0d0
Below is the systemlog file :
root@a7dmc:/var/adm/syslog > /opt/resmon/bin/resdata -R 155713541 -r /storage/events/enclosures/gazemon/0_1_1_0.0.0... (11 Replies)
Discussion started by: kekanap
11 Replies
3. Solaris
Not too familiar with VxVM. We have a Device c1t0d0, disk rootdg01, group rootdg that was paired with Device c1t1d0, disk mirror_1, group rootdg.
c1t0d0 has failed.
When we get a replacement for c1t0d0 can we just run vxdiskadm and choose choice #5 to "replace a failed or removed disk" ?
... (9 Replies)
Discussion started by: pzxkys
9 Replies
4. Solaris
I need to corrupt a superblock of a mounted device in a soalris m/c and check recovery from an alternate superblock. How can this be done? (2 Replies)
Discussion started by: sujathan
2 Replies
5. Solaris
hi guys,
i was doing a fresh installation of vxvm 4.0 on solaris 8 Sun enterprise 3500 and when i ran vxinstall command it gave me option of appdg and appdg02 to be encapsulated . I wanted to encapsulate rootdg. i wrongly encapsulated appdg. is there any work around for this ?
your response... (5 Replies)
Discussion started by: ishila
5 Replies
6. UNIX for Dummies Questions & Answers
Hmm, how to ask this without sounding too malicious...
How might one go about causing a disk corruption in OS X specifically or via the command line in UNIX in general?
Doesnt matter the severity of the problem, I just want to scare the person a little, then fix the problem for them.
Any... (1 Reply)
Discussion started by: Yummator
1 Replies
7. UNIX for Dummies Questions & Answers
Hi guys,
For some reason a client has given us a Sun Netra T1 with Solaris 8 to administer for them. That's always good business. However, the other day we rebooted the machine and to our amazement, after doing the preliminary hardware tests, we got an error messgae saying that /etc/inittab was... (3 Replies)
Discussion started by: Ivo
3 Replies
8. Cybersecurity
Help!
SCO Unix 5.05.
A relatievely new system went down on me today. I got the dreaded error:
Out of Space on Device (1/42).
I was able to clear up some space in the /tmp directory, however, when I try to boot, the system prompts me to go into single user mode and I get the... (2 Replies)
Discussion started by: gseyforth
2 Replies
9. UNIX for Dummies Questions & Answers
Thank you livin Free for all your help. We removed a lot of spool files and report files. Which should have freed up some space.
But now I think a major problem we have is we have lost or corrupt files which are preventing us from coming up correctly. Can we load or can you copy us a directory... (1 Reply)
Discussion started by: NOT A CLUE
1 Replies
voldctl(8) System Manager's Manual voldctl(8)
NAME
voldctl - Controls the volume configuration daemon
SYNOPSIS
/sbin/voldctl init [hostid]
/sbin/voldctl hostid hostid
/sbin/voldctl add disk accessname [attr[=value]]...
/sbin/voldctl rm disk accessname...
/sbin/voldctl list
/sbin/voldctl enable
/sbin/voldctl disable
/sbin/voldctl [-k] stop
/sbin/voldctl mode
/sbin/voldctl license [init]
DESCRIPTION
The voldctl utility manages some aspects of the state of the volume configuration daemon, vold, and manages configuration aspects related
to bootstrapping the rootdg disk group configuration.
A key part of the state of vold and of bootstrapping the rootdg disk group is the /etc/vol/volboot file. This file contains a host ID,
which is usually the host name, that LSM uses to establish ownership of physical disks. This host ID is used to ensure that two or more
hosts that can access disks on a shared SCSI bus will not interfere with each other in their use of those disks. This host ID is also
important in the generation of some unique ID strings that are used internally by the Logical Storage Manager for stamping disks and disk
groups.
The /etc/vol/volboot file may also contain a list of disks to scan in search of the rootdg disk group. This list is only needed if the
autoconfiguration functionality of LSM is disabled (see vold(8) for details). At least one disk in the list must be both readable and a
part of the rootdg disk group, or the Logical Storage Manager will not be able to start up correctly.
The vold daemon operates in one of three modes: enabled, disabled, or booted. The enabled state is the normal operating state. Most con-
figuration operations are allowed in the enabled state. Entering the enabled state imports all disk groups that were previously imported on
this host, and begins the management of device nodes stored in the /dev/vol and /dev/rvol directories.
In the disabled state, vold does not retain configuration information for the imported disk groups, and does not maintain the volume device
directories. Most operations are disallowed in the disabled state. Certain failures, most commonly the loss of all disks or configuration
copies in the rootdg disk group, will cause vold to enter the disabled state automatically.
The booted state is entered as part of normal system startup, prior to checking the root file system (see fsck(1)). Entering the booted
mode imports the rootdg disk group, and then waits for a request to enter the enabled mode. The volume device node directories are not
maintained in booted mode, because it may not be possible to write to the root file system.
KEYWORDS
The action performed by voldctl depends upon the keyword specified as the first operand. Supported keywords are: Reinitializes the
/etc/vol/volboot file with a new host ID (which is usually the host name), and an empty list of disks. If a hostid operand is specified,
this string is used; otherwise, a default host ID is used. On systems with a hardware-defined system ID, the default host ID might be
derived from this hardware ID. Changes the host ID, which is usually the host name, in the /etc/vol/volboot file and on all disks in disk
groups currently imported on this machine. It may be desirable to change the Logical Storage Manager host ID for your machine if you are
also changing the network node name of your machine.
If some disks are inaccessible at the time of a hostid operation, it may be necessary to use the voldisk clearimport operation to
clear out the old host ID on those disks when they become reaccessible. Otherwise, you may not be able to re-add those disks to
their disk groups.
Note
Take care when using this command. If the system crashes before the hostid operation completes, some disk groups may not reimport
automatically. Adds to the list of disks in the /etc/vol/volboot file. Disks are specified based on their disk access name. This
name identifies the physical address of the disk. For example, to add disk dsk3c you might use the command: /sbin/voldctl add disk
dsk3c
If there is a disk access record in the rootdg configuration for the named disk, configuration parameters are taken from that
record. Otherwise, it may be necessary to specify some attributes to voldctl add disk. Removes one or more disks from the
/etc/vol/volboot file. Disks are specified based on the name used in the corresponding voldctl add disk operation. Lists the con-
tents of the /etc/vol/volboot file. This list includes the host ID (which is usually the host name), some sequence numbers, and the
list of disks and disk attributes stored in the /etc/vol/volboot file. Requests that vold enter enabled mode, import all disk
groups that were previously imported on this host, and rebuild the volume device node directories. This operation can be used even
if vold is already in enabled mode, however any deported disk groups remain deported. The primary purpose for using this operation
when in enabled mode is to rebuild the volume device nodes. This operation will also cause vold to scan for any disks that were
newly added since vold was last started. In this manner, disks can be dynamically configured to the system and then recognized by
the Logical Storage Manager.
If this operation fails, voldctl exits with the appropriate error status and displays an error message. Requests that vold enter
disabled mode. This may be necessary to perform some maintenance operations. This does not disable any configuration state loaded
into the kernel. It only prevents further configuration changes to loaded disk groups until vold is re-enabled. Requests that vold
exit. This may be necessary to reset the Logical Storage Manager, such as using the -r reset option to vold. This does not disable
any configuration state loaded into the kernel. It only affects the ability to make configuration changes until vold is restarted.
If the -k option is used vold will be stopped by sending it a SIGKILL signal. The command will delay for up to 1 second to verify
that vold has exited. After 1 second if vold has not exited an error will be returned. Prints the current operating mode of vold.
The output format is:
mode: operating_mode
where operating_mode is either enabled, disabled, booted, or not-running. With an argument of init, requests that vold re-read any
persistently stored license information. If licenses have expired, this may cause some features to become unavailable. If new
licenses have been added, this will make the features defined in those licenses available.
With no arguments, voldctl license prints the list of features which are currently available based on known licensing information.
SEE ALSO
volintro(8), vold(8), voldg(8), voldisk(8), signal(4)
voldctl(8)