10-21-2004
thanks for reply
I have no free slice on the internal disk. is they a work around this?
i have only one internal disk which has the Os installed and metadb needs to the spread across as many disk as possible, at least two disk.
How can i solve this problem?
Thanks in advance
7 More Discussions You Might Find Interesting
1. Solaris
Hi,
Going to be applying patches to Sun prod (dev 1st) boxes soon,
I'm going to break the mirror's on 3 file systems on the root disk prior to that (/, /var, /swap),then run 9_Recommended. Then, run it for a day or 2 before re-syncing the mirrors.
But, what if I want to backout of this... (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies
2. UNIX for Dummies Questions & Answers
Hey there,
I am starting a Computer Science Foundation year at the end of this month and am trying to get a little bit ahead of the game. I have always wanted to learn Unix and am currently struggling with creating a boot disc to run Solaris (I have chosen to study this) from as opposed to... (0 Replies)
Discussion started by: Jupiter
0 Replies
3. Solaris
I am new to Sun.
I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor?
Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies
4. Solaris
I've looked a little but haven't found a solid answer, assuming there is one.
What's better, hardware mirroring or ZFS mirroring? Common practice for us was to use the raid controllers on the Sun x86 servers. Now we've been using ZFS mirroring since U6. Any performance difference? Any other... (3 Replies)
Discussion started by: Lespaul20
3 Replies
5. Solaris
Hi everyone,
Normally it always easier in Sparc machine, i can set or manually use the boot-device in NVram to boot the mirrored disk. However I have a big trouble about x86 mirror for a long time. I have been doing anything i can: search document, google, ask the others.
Recently i did as... (5 Replies)
Discussion started by: tien86
5 Replies
6. Solaris
Hi ,
I am new to SVM .when i try to learn RAID 1 , first they are creating two RAID 0 strips through
metainit d51 1 1 c0t0d0s2
metainit d52 1 1 c1t0d0s2
In the next step
metainit d50 -m d51
d50: Mirror is setup
next step is
metaattach d50 d52
d50 : submirror d52 is... (7 Replies)
Discussion started by: vr_mari
7 Replies
7. HP-UX
what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 Replies
LEARN ABOUT OSF1
disklabel
disklabel(4) Kernel Interfaces Manual disklabel(4)
NAME
disklabel - Disk pack label
SYNOPSIS
#include <sys/disklabel.h>
DESCRIPTION
Each disk or disk pack on a system may contain a disk label which provides detailed information about the geometry of the disk and the par-
titions into which the disk is divided. It should be initialized when the disk is formatted, and may be changed later with the disklabel
program. This information is used by the system disk driver and by the bootstrap program to determine how to program the drive and where
to find the file systems on the disk partitions. Additional information is used by the file system in order to use the disk most effi-
ciently and to locate important file system information. The description of each partition contains an identifier for the partition type
(standard file system, swap area, etc.). The file system updates the in-core copy of the label if it contains incomplete information about
the file system.
The label is located in sector number LABELSECTOR of the drive, usually sector 0 (zero) where it may be found without any information about
the disk geometry. It is at an offset LABELOFFSET from the beginning of the sector, to allow room for the initial bootstrap. The disk
sector containing the label is normally made read-only so that it is not accidentally overwritten by pack-to-pack copies or swap opera-
tions; the DIOCWLABEL ioctl, which is done as needed by the disklabel program, allows modification of the label sector.
A copy of the in-core label for a disk can be obtained with the DIOCGDINFO ioctl; this works with a file descriptor for a block or charac-
ter (raw) device for any partition of the disk. The in-core copy of the label is set by the DIOCSDINFO ioctl. The offset of a partition
cannot generally be changed, nor made smaller while it is open. One exception is that any change is allowed if no label was found on the
disk, and the driver was able to construct only a skeletal label without partition information. Finally, the DIOCWDINFO ioctl operation
sets the in-core label and then updates the on-disk label; there must be an existing label on the disk for this operation to succeed.
Thus, the initial label for a disk or disk pack must be installed by writing to the raw disk. All of these operations are normally done
using the disklabel program.
RELATED INFORMATION
Files: disktab(4)
Commands: disklabel(8) delim off
disklabel(4)