[root@localhost] /work/users> metastat -c d103
d103 p 32GB d100
d100 m 68GB d101 d102
d101 s 68GB c1t2d0s0
d102 s 68GB c1t3d0s0

[root@localhost] /work/users> metastat -p d103
d103 -p d100 -o 32 -b 58720256 -o 127926432 -b 8388608
d100 -m d101 d102 1
d101 1 1 c1t2d0s0
d102 1 1 c1t3d0s0

So from the first metastat -c d103.. that’s a mirrored 68G partition, d100 and a 32G soft partition d103.. We still have around 35G of space.

update: — someone comment please.. this information is incomplete!

Anyway, the link will forward you to a form where you need to fill up some personal information (it’s from Sun, so there will be no selling of email or spamming there). Once you’re done with that, go read and study Solaris Virturalization!

Enjoy!

» Download your free copy of Virtualization for Dummies.

This How-To Guide instructs users, system administrators, and developers unfamiliar with Solaris 10 OS on consolidating applications onto a single server using Solaris Containers technology. The guide starts with a brief overview of Solaris Containers and follows with an example of using Solaris Containers to consolidate two Web server applications and an email server application onto a single server. Users are guided step-by-step through the consolidation process, with code examples and illustrations.

After using this guide, a user should be able to create Solaris Containers by:

* Creating a resource pool
* Defining Solaris Zones
* Assigning CPU usage with the Fair Share Scheduler (FSS)
* Installing and booting a zone
* Configuring access to raw devices from the zone

I wont be able to post every info from the PDF file here.. But I can however maybe put a part so that it will entice you more to download the paper:

Solaris Zones
As part of the consolidation effort, it is important to
evaluate the needs of the applications that will share the
consolidated system. In this example, the email server and
Web server applications need to run in isolated
environments that make it appear as if they are running on
physically separate machines. This is made possible by a
Solaris Container technology called Solaris Zones, which
provides separate environments on a machine and logically
isolates applications from one another. Each application
receives a dedicated namespace in which to run, and
cannot see, monitor, or affect applications running in
another zone

Dynamic Resource Pools
In this example there are two types of applications, one
that needs a fully dedicated CPU—an email server, and
another that is more flexible and can share CPUs—the two
Web servers. To accomplish these different levels of
isolation we use a Solaris Container technology called
Dynamic Resource Pools that enables CPU resources to be
dedicated to specific applications. In this example, the
email server needs a separate resource pool, while the Web
servers can share another

Fair Share Scheduler
While the two Web servers are capable of sharing the
remaining CPUs on the system, they each need a minimum
guarantee of CPU resources that will be available to them.
This is made possible by another Solaris Container
technology called the Fair Share Scheduler (FSS). This
software enables CPU resources to be allocated
proportionally to applications. That is, each application
gets assigned a number of the available “shares” of the
total CPU.

And many more! Excited yet? here’s the link for download:

https://www.sun.com/offers/details/solaris_containers.xml?cid=927534

Yesterday we had to replace a failed disk that belongs to a mirror. The disk is running in a Sparc Solaris 10 box. It’s a 72GB from Fujitsu

c1t1d0           Soft Errors: 440 Hard Errors: 12 Transport Errors: 124
Vendor: FUJITSU  Product: MAY2073RCSUN72G  Revision: 0501 Serial No: 0711S0935R
Size: 73.40GB <73400057856 bytes>

As you can see from the iostat -En command, the disk is spitting hard errors and must be replaced before it can cause a lot more headache. It’s in c1t1, right.

Here’s what we’re supposed to do:

• we could delete the meta data base that corresponds to the failed disk
• detached the failed disk/slices to the mirror
• clear it
• unconfigure the disk
• replace the disk
• configure the disk
• create new meta device database
• Initialize the disk
• Attached it to mirror
• and sync

Here’s the detailed job:

Info:
metadb | grep c1t1
metadb –d c1t1d0s7

Detach:
metadetach d30 d32
metadetach d40 d42
metadetach d20 d22
metadetach d10 d12

metaclear d32
metaclear d42
metaclear d22
metaclear d12

Verify:
metastat -p | grep c1t1d0
metadb | grep c1t1d0
[root@localhost] /> cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 CD-ROM connected configured unknown
c1 scsi-bus connected configured unknown
c1::dsk/c1t0d0 disk connected configured unknown
c1::dsk/c1t1d0 disk connected configured unknown
c1::dsk/c1t2d0 disk connected configured unknown
c1::dsk/c1t3d0 disk connected configured unknown
usb0/1 unknown empty unconfigured ok
usb0/2 unknown empty unconfigured ok
usb1/1.1 unknown empty unconfigured ok
usb1/1.2 unknown empty unconfigured ok
usb1/1.3 unknown empty unconfigured ok
usb1/1.4 unknown empty unconfigured ok
usb1/2 unknown empty unconfigured ok

Unconfigure:
cfgadm -c unconfigure c1::dsk/c1t1d0

Verify ulit, note the red text above:
cfgadm –al
SWAP DISK

Undo what has been done….

Configure:
cfgadm -c configure c1::dsk/c1t1d0

format (to label disk)

prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s – /dev/rdsk/c1t1d0s2

metadb -a –c 2 c1t1d0s7

Attach!!

metainit d32 1 1 c1t1d0s6
metainit d42 1 1 c1t1d0s4
metainit d22 1 1 c1t1d0s1
metainit d12 1 1 c1t1d0s0
metattach d30 d32
metattach d40 d42
metattach d20 d22
metattach d10 d12
metastat -p
metadevadm -u c1t1d0

And you’re done! Grab a cup of coffee and wait till the synchronization is done.