SVM: Determine Free Space on Soft Partition , we use the metastat -c command…

[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!

I just want to share a link for those who are not subscribe to the official Sun Microsystems’ email newletter.. (what?! You’re not subscribed?!)

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.

I am subscribe to the official Sun Microsystem newsletter and I got this one directly from my inbox that I want to share to every Solaris SysAdmin out there:

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

Read the rest of this entry »

This one is about Solaris Volume Manager and all those meta commands you can think of.. (metadb, metadettach, metattach, metaclear etc)…

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:

Read the rest of this entry »