backend is the location where data of a virtual disk are stored. The backend can be a disk,
a disk slice, a file, a volume (including ZFS, SVM, or VxVM), or any disk pseudo device. The disk label
can be SMI VTOC, EFI, or no label at all. A backend appears in a guest domain either as a full disk or
as single slice disk, depending on whether the slice option is set when the backend is exported from
the service domain. When adding a device, the volume-name must be paired with the backend.
So I guess you can specify c0t600508A400070E320002200100170000d0 as backend.
Hi there
I am about to mirror a Solaris 10 x86 box (SunFire X4100) onto a secondary disk using svm (current system is one disk). My question is this, on X86 boxes there is a slice 8 defined as boot partition (and also a slice 9, dunno what its used for tho). Do I need to mirror this boot slice... (0 Replies)
Is it possible to create a Mirror with zfs ??
I'm experimented user with Solstice Disk suite.
Or Sun Volume manager or veritas volume manager.
But, i would like switch from Disksuite to Zfs.
All my mirrored disks. (1 Reply)
Hi,
Recently I faced with need of analyze root disk. I figured out two possible ways to do it:
1. Practical. Boot from CD and run format
2. Theoretical. Create live upgrade boot environment on another disk, activate it, reboot, unmont all root disk partitions and run format.
I've already... (3 Replies)
I am a new Unix Sys Admin who is learning mostly from books with minimal classroom training (ie: no certificates, training is largely hands-on, conducted at work). I work with Solaris 8 through 10, and with some fairly outdated hardware. In my work restoring old workstations I have been instructed... (2 Replies)
Hi Folks,
I am trying to make a script to assign all diskspace to slice 0, on multiple sized disks. Since the disks are new they may need to be labelled also to avoid the error: Cannot get disk geometry
Below is my code struggling with logic which doesn't seem to be producing the desired... (0 Replies)
Hi there,
I am trying to do root volume mirroring on SunFire V210 server. I have two disks in it.First one is c1t0do and second one is c1t1do. Both disks already have partitions in them so I am deleting the partitions of second disk(c1t1do) using format command and selecting cylinder start 0... (2 Replies)
Hi all,
I am using SPARC Solaris 11.1 with EFI labelled disks.
I am new to ZFS file systems and slightly stuck when trying to create a partition (slice) on one of my LUNs.
EFI labels use sectors and blocks and I am not sure how exactly it works.
From here I can try and create a... (2 Replies)
Hi,
How to to make a slice and define as ufs from zpool? Please advice me.
Thanks.
---------- Post updated at 01:53 AM ---------- Previous update was at 12:24 AM ----------
Before slice:
Part Tag Flag Cylinders Size Blocks
0 root wm 0 ... (2 Replies)
I have a 240GB disk as rpool. I have installed Solaris 11.3 to a partition which is 110GB. Now I have another 130GB which is unallocated. I want to use that additional space as a temporary folder to be shared between Solaris and Linux. The additional space had no /dev/dsk/c2t4... entry so I used... (8 Replies)
Discussion started by: kebabbert
8 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)