09-02-2011
Installing using ZFS - need to remove EFI disk labels
What is the preferred way of doing this from a bare metal install?
6 More Discussions You Might Find Interesting
1. Solaris
Hi Peeps,
Can anyone help me an EFI lablel on a 3510 raid array that I cannot get rid of, format -e and label just asks you if you want to label it. Want an SMI label writing to it.
Anyone got any ideas on how to remove the EFI label?
Thanks in advance
Martin (2 Replies)
Discussion started by: callmebob
2 Replies
2. Solaris
Hello, I am new to Solaris so i apologize upfront if my questions seem trivial.
I am trying to install a ZFS file system on a Solaris 10 machine with UFS already installed on it.
I want to run: # zpool create pool_zfs c0t0d0
then: # zfs create pool_zfs/fs
My question is more to... (3 Replies)
Discussion started by: mcdef
3 Replies
3. Solaris
Hi All!
I have been tasked with creating a clustered file system for two systems running Sol 10 u8. These systems have 3 zones each and the global zone has ZFS on the boot disk. We currently have one system sharing an NFS mount to both of these systems.
The root zfs pool status (on the... (2 Replies)
Discussion started by: bluescreen
2 Replies
4. Solaris
I accidently added a disk in different zpool instead of pool, where I want.
root@prtdrd21:/# zpool status cvfdb2_app_pool
pool: cvfdb2_app_pool
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
cvfdb2_app_pool ONLINE 0 0 0... (1 Reply)
Discussion started by: solaris_1977
1 Replies
5. Solaris
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)
Discussion started by: selectstar
2 Replies
6. Solaris
Hi all,
I have a EFI disk and it is use in zfs pool.
partition> p
Volume: rpool
Current partition table (original):
Total disk sectors available: 1172107117 + 16384 (reserved sectors)
Part Tag Flag First Sector Size Last Sector
0 usr wm ... (8 Replies)
Discussion started by: javanoob
8 Replies
PHSEG(3) MBK PHYSICAL STRUCTURE DEFINITIONS PHSEG(3)
NAME
phseg - mbk physical segment
DESCRIPTION
The phseg structure is used to describe a segment belonging to a symbolic layout model, see phfig(3) for details. Transistors are segments
of a particular layer.
The declarations needed to work on phseg are available in the header file "/labo/include/mph402.h", where '402' is the actual mbk version.
The following C structure supports the description of the segment :
typedef struct phseg {
struct phseg *NEXT;
char *NAME;
long X1,Y1,X2,Y2;
long WIDTH;
char TYPE;
char LAYER;
struct ptype *USER;
} phseg_list;
NEXT Pointer to the next segment in the list.
NAME Name of the segment. The name is not an identifier, and a name is present only if the designer used one for debug pur-
poses.
X1, Y1, X2, Y2 Coordinates of each end of the segment. Since it's a symbolic segment, one alway has either X1 = X2 or Y1 = Y2. Fur-
thermore, by construction, it is warranty, if one accesses the data structure through the legal functions, that X1 <=
X2 and Y1 <= Y2.
TYPE This caracter can take four values :
LEFT or RIGHT if Y1 = Y2. The exact value is chosen by addphseg, depending upon X1 and X2 relations.
UP or DOWN if X1 = X2
LAYER Symbolic layer used for the segment. The legal values are :
NWELL N bulk
PWELL P bulk
NTIE N implant in P bulk
PTIE P implant in N bulk
NDIF N diffusion
PDIF P diffusion
NTRANS N transistor
PTRANS P transistor
POLY polysilicium
ALU1 first metal
ALU2 second metal
ALU3 third metal
TPOLY polysilicum through route
TALU1 first metal through route
TALU2 second metal through route
TALU3 third metal through route
WIDTH Width of the segment. The physical extension of a segment is perpendicular to its direction.
USER Pointer to a ptype list, see ptype for details, that is a general purpose pointer used to share informations on the
segment.
SEE ALSO
mbk(1), addphseg(3), getphseg(3), delphseg(3), phfig(3), ptype(3).
BUG REPORT
This tool is under development at the ASIM department of the LIP6 laboratory.
We need your feedback to improve documentation and tools.
ASIM
/LIP6 October 1, 1997 PHSEG(3)