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
volsetup(8) System Manager's Manual volsetup(8)
NAME
volsetup, lsmsetup - Initializes Logical Storage Manager (LSM) by creating the rootdg disk group
SYNOPSIS
/usr/sbin/volsetup [-c] [-o force] [-n num] [-s] [diskname | partition...] [attribute...]
OPTIONS
The following options are recognized: Clears the lock protecting multiple nodes in a cluster from simultaneously running the volsetup com-
mand. After clearing the lock, it is taken out on behalf of the initiating node. Specifies the approximate number of disks to be managed
by LSM. This option is currently ignored and is only provided for compatibility with existing scripts. Forces re-initialization if LSM has
already been initialized. Synchronizes a node with cluster members.
DESCRIPTION
The volsetup script is an interactive script that should be run after installing LSM. The diskname or partition parameter specifies the
name of at least one disk or partition to be used in creating the rootdg disk group. If no disk or partition name is given on the command
line, the volsetup script prompts for this information.
If more than one disk name or partition name is given as input, all the disks and partitions are added to the rootdg disk group.
The -o force option can be used to remove an existing LSM configuration and reinitialize LSM.
The volsetup script starts the vold daemon and one voliod daemon per CPU by default. After volsetup has been run, LSM is fully functional.
To configure LSM in a TruCluster Version 5.0 multi-member cluster, run the volsetup command from one of the cluster members and run the
volsetup -s on the other cluster members. If additional members are later added to the cluster with the clu_add_member utility, do not run
volsetup -s command on the new member. The clu_add_member utility automatically synchronizes LSM on the new node.
ATTRIBUTES
The following attributes can be specified to affect the layout strategy used by volsetup: Specifies the length of the public area to create
on the disk. This defaults to the size of the disk minus the private area on the disk. Specifies the length of the private area to create
on the disk. The default is 4096 sectors. Specifies the number of configuration copies and log copies to be initialized on the disk. The
number of configuration copies will be the same as the number of log copies. This defaults to 1. Specifies the length in sectors of each
configuration copy. The default values are calculated based on the value of nconfig. Specifies the length in sectors of each log copy.
The default values are calculated based on the value of nconfig. Specifies a user-defined comment.
ERRORS
You may receive the following messages when using the volsetup command. LSM initialization fails if none of the disks specified can be ini-
tialized by LSM.
The following message indicates that LSM is initialized on the system. To reinitialize LSM, use the -o force option, which removes previ-
ous LSM configuration. A previous LSM configuration exists (err=22). Use the "-o force" option to reinitialize LSM. Stop.
The following message indicates that you tried to initialize an LSM disk on a partition or on a disk that is actively in use. The partition
could be a mounted UFS or AdvFS filesystem that is initialized as an LSM disk or used as a swap device. special-device or an overlapping
partition is open.
The following message indicates that you tried to initialize an LSM disk on a partition that is not currently in active use, but is marked
for use in the disk label's partition map. For example, the partition may be part of a UFS filesystem (4.2BSD) or an AdvFS domain. spe-
cial-device is marked in use for fstype in the disklabel. If you continue with the operation you can possibly destroy existing data CON-
TINUE? [y/n]
If you know that the partition you specified to volsetup does not contain any data, you can choose to override the warning. In this case,
the fstype in the disk label is modified to an LSM fstype such as LSMsimp, LSMpubl or LSMpriv. The exact fstype depends on whether a disk
or a partition is given as an argument to voldisksetup.
Note that you can use the command disklabel -s to set the fstype in the disk label to unused for partitions that do not contain any valid
data. See disklabel(8) for more information.
The following message indicates that the partition you specified is not marked for use, but other, overlapping partitions on the disk are
marked for use. Partition(s) which overlap special-device are marked in use. If you continue with the operation you can possibly destroy
existing data. CONTINUE? [y/n]
If you override this warning, the fstype in the disk's label is modified. The partition you specified to volsetup will be marked as in use
by LSM and all overlapping partitions will be marked UNUSED.
The following examples illustrate these messages: Initializing an LSM disk on a partition that is open and actively in use:
# /usr/sbin/volsetup dsk11c
dsk11c or an overlapping partition is open. Initializing an LSM sliced disk on a disk which has partition g marked for use by UFS
(4.2BSD):
# /usr/sbin/volsetup dsk11
/dev/rdisk/dsk11g is marked in use for 4.2BSD in the disklabel. If you continue with the operation you can possibly destroy exist-
ing data. CONTINUE? [y/n]
Partition g of disk dsk11 is marked for use by UFS (4.2BSD). If UFS is not actively using this partition and the partition does not
contain any data, you may want to override this warning, by answering y. In this case, partition g will be marked as LSMpubl and
partition h will be marked as LSMpriv in the disk label. Initializing an LSM simple disk on a partition whose overlapping parti-
tions are marked for use:
# /usr/sbin/volsetup dsk11c
Partition(s) which overlap /dev/rdisk/dsk11c are marked in use. If you continue with the operation you can possibly destroy exist-
ing data. CONTINUE? [y/n]
Partition c, which is being initialized into LSM, is not currently in use, but other partition(s) which overlap with partition c are
marked in use in the disk label. If you answer y, partition c on disk dsk11 will be marked LSMsimp in the disk label and all parti-
tions that overlap partition c will be marked UNUSED. Initializing an LSM disk on a disk that has no disk label:
# /usr/sbin/volsetup dsk11
The disklabel for dsk11 does not exist or is corrupted. Quitting...
See disklabel(8) for information on installing a disk label on a disk.
EXAMPLES
The following is an example of volsetup usage :
# /usr/sbin/volsetup dsk3 dsk8h
This will add disk dsk3 and partition dsk8h to the rootdg disk group.
SEE ALSO
disklabel(8), volintro(8), vold(8), voliod(8)
volsetup(8)