-My Daily Tidbits-

My Kids

2009-10-23T12:37:00.001+08:00

Enabling large file support dynamically with VxFS

2009-02-20T14:35:00.001+08:00

I recently encountered a VxFS file system that didn’t support largefiles. This issue was causing one of our Oracle databases to complain, which was preventing us from using datafiles optimized for our application access patterns. Since the file system was a Veritas File System (VxFS), I was able to fix this problem with the fsadm utility:

$ /usr/lib/fs/vxfs/fsadm -F vxfs -o largefiles /u01

$ mount -p | grep u01
/dev/vx/dsk/oradg/oravol01 - /u01 vxfs - no rw,suid,delaylog,largefiles,ioerror=mwdisable

This operation can be run against mounted live file systems, which is great for production environments.

Solaris notes

2009-02-20T07:38:00.004+08:00

Disk Identification

The /dev/dsk and /dev/rdsk directories are checked for disk partition entries - that is, symbolic links with names of the form cN[tN]dNsN, where N represents a decimal number.

cN is the logical controller number, an arbitrary number assigned by this program to designate a particular disk controller. The first controller found on the first occasion this program is run on a system, is assigned number 0.

tN is the bus-address number of a subsidiary controller attached to a peripheral bus such as SCSI or IPI (the target number for SCSI, and the facility number for IPI controllers).

dN is the number of the disk attached to the controller, and

sN is the partition, or slice, number of the entry.

c0t0d0s0

c - controller

t - target (e.g. scsi target)

d - disk (usually 0)

s - slice

To map sd? style disk names to this format, check the link displayed on a long listing.

ls -l /dev/sd?c

Solstice disk suite
The disk suite package normally lives in /usr/opt/SUNWmd/usr/sbin. Add this to the PATH of the root user

PATH=$PATH:/usr/opt/SUNWmd/usr/sbin; export $PATH

The examples for mirror disks use the idea of a "mirror top". This is the metadisk which is actually mounted, as opposed to the two "sides" of the mirror.
Decoding the md.tab

concatentation of 2

d7 2 1 /dev/dsk/c0t0d0s0 1 /dev/dsk/c1t0d0s0

stripe of 2, with 16k interlace

d8 1 2 /dev/dsk/c0t0d0s0 /dev/dsk/c1t0d0s0 -i 16k

concat of 2 stripes of 2

d3 2 2 /dev/dsk/c0t0d0s0 /dev/dsk/c1t0d0s0 -i 16k \
2 /dev/dsk/c0t0d1s0 /dev/dsk/c1t0d1s0

i.e. dx

mirror

d1 -m d2

where d1 is top
Activating the md.tab

metainit -a will read whole file

metainit d2 will initialise given disk

metainit d2 will initialise top of mirror

metattach d1 d3 will attach other side of mirror (synch done in background)

To detach one side of a mirror

metadetach [ -f ]

To attach the "second side"

metattach

Note that the newly attached side resilvers in the background automatically. Therefore, if multiple mirrors exist on the same physical disk beware of maxing out the IO on the physical drive if re-attaching multiple mirrors. It is possible to check the current amount of work complete as follows:

metstat | grep %

To clear errors on a metadisk
This procedure should only be applied where the error state is a result of SCSI errors - not when there is an actual error on the disk.

Note also that this process should only be applied for an unmounted disk.

metaclear clears the mdisk from the metadb. The reference will still exist in /usr/opt/SUNWmd/md.tab.

metainit re-reads the info in md.tab and activates the mdisk.

e.g.

# metastat d0
d0: Mirror
Submirror 0: d32
State: Needs maintenance
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4140480 blocks

d32: Submirror of d0
State: Needs maintenance
Invoke: after replacing "Maintenance" components:
metareplace d0 c1t4d0s1
Size: 4140480 blocks
Stripe 0: (interlace: 64 blocks)
Device Start Block Dbase State Hot Spare
c1t3d0s0 0 No Okay
c1t4d0s1 0 No Last Erred
c1t5d0s3 0 No Last Erred

# umount
# metaclear -r d0
# metainit d32
# metainit d0
# mount

To clear a mirror disk where one is in maintenance/one in last err
This procedure should only be applied where the error state is a result of SCSI errors - not when there is an actual error on the disk.

metareplace -e /dev/dsk/c?td?s? where this is the maintenance side of the mirror.

Await resynching, then repeat for the last erred side of the mirror.

e.g.

# metastat d0

d0: Mirror
Submirror 0: d32
State: Needs maintenance
Submirror 1: d33
State: Needs maintenance
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 4149600 blocks

d32: Submirror of d0
State: Needs maintenance
Invoke: metareplace d0 c1t0d0s0
Size: 4149600 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t0d0s0 0 No Maintenance

d33: Submirror of d0
State: Needs maintenance
Invoke: after replacing "Maintenance" components:
metareplace d0 c1t1d0s0
Size: 4149600 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t1d0s0 0 No Last Erred

# metareplace -e d0 /dev/dsk/c1t0d0s0
# #wait
metareplace -e d0 /dev/dsk/c1t1d0s0

Boot
Boot Block

To install the boot information at the start of a given disk (in a reserve area, so data is not overwritten)

installboot /usr/platform//lib/fs/ufs/bootblk /dev/rdsk/c?t?d?s?

where architecture is like sun4d . This can be ascertained from uname -m
prtdiag

prtdiag displays system configuration and diagnostic information.

/usr/platform//sbin/prtdiag -v

where architecture is like sun4d . This can be ascertained from uname -a

The boot prompt is ok
The boot command

boot for full, normal, multiuser
-r to reconfigure device tree (if devices added or removed)
-s single user
-v verbose
-w writable (for cdrom boot)
-a interactive - rarely used, this option asks location of kernel, root filesys type, etc

boot cdrom -svwr to boot from cdrom, single user,verbose, writable fsys, build device tree

boot kadb to boot with lkernel debugger
Getting to the prom
To be precise, ok is the "prom prompt" rather than the "boot prompt" but mostly, we just want to boot when there is an ok prompt. Sometimes, you may need to get to the prom on a running system. The method depends on the console you have. If it is a proper Sun console, there's a good chance that stop-A will work. Otherwise, try F5, Break or L1-A. Be aware that this can hang or kill the system, so use it with caution.
A hanging system
If the system is hanging or you are trying to crash it, be sure to sync the system before rebooting. This way, you have a chance of getting a core dump as the system comes back up.

ok sync

After reboot, if you don't have enough room in /var/crash (and, really, you should have a /var/crash which is larger than physical memory), you can attempt a manual savecore to another area.

e.g.

# cd /spare
# savecore -d .

While you're at the prom level

banner for additional info

reset run hardware diagnostics and reboot

help [command] list of commands or help on given command

probe-scsi-all look for attached SCSI devices

test [device|device-type] run selftests on device e.g. test net

printenv all bootflags

setenv e.g. setenv auto-boot? False

eeprom is the os-level equivalent of printenv and setenv

e.g.

eeprom auto-boot\?=false

Disk Formatting
Disk geometry

An example disk geometry from /etc/format.dat

disk_type = "SUN9.0G" \
: ctlr = SCSI : fmt_time = 4 \
: ncyl = 4924 : acyl = 2 : pcyl = 4926 : nhead = 27 \
: nsect = 133 : rpm = 7200

disk_type is a label

ncyl - number of cylinders available

acyl - additional cylinders

pcyl - ?

nhead - number of heads

nsect - number of sectors per track: 1 sector = 1 block = 512 bytes

rpm - rpm

nsect * nhead = blocks per cylinder

ncyl * nsect * nhead / 2048 = useable space in Mb
VTOC

An example VTOC from /etc/format.dat

partition = "SUN9.0G_4-4GB"\
: disk = "SUN9.0G" : ctlr = SCSI\
: 2 = 0, 17682084\
: 0 = 0, 8618400\
: 1 = 2400, 438102\
: 3 = 2522, 8618400\
: 7 = 4922, 7182

partition is a label

disk matches a defined disk geometry

= , \

where \ is a continuation character

length in blocks should be a multiple of nsect * nhead

partition 2 is the whole disk. Length in blocks of partition 2 should be equal to useable size i.e. nsect * nhead * ncyl Note that with the format menu, the shortest unique string will do - a is sufficient rather than analyze below.

It is often easier to use fmthard to duplicate a disk format

prtvtoc /dev/rdsk/c1t0d0s2 > /tmp/vtoc

fmthard -s /tmp/vtoc /dev/rdsk/c1t1d0s2

# format
Specify disk (enter its number): 3
selecting c0t3d0
[disk formatted]
Warning: Current Disk has mounted partitions.

FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
quit
format> analyze

ANALYZE MENU:
read - read only test (doesn't harm SunOS)
refresh - read then write (doesn't harm data)
test - pattern testing (doesn't harm data)
write - write then read (corrupts data)
compare - write, read, compare (corrupts data)
purge - write, read, write (corrupts data)
verify - write entire disk, then verify (corrupts data)
print - display data buffer
setup - set analysis parameters
config - show analysis parameters
quit

Package info

/var/sadm/install/contents holds details of all packages on the system. pkginfo gives list of packages installed.
Photon arrays

Minimal configuration is 5 disks. The first slots to be filled must be 3 and 6 at the front and 0,3 and 6 in the back. This minimum configuration is a requirement because circuitry on the disk drives regenerate and retime the data signals which corrects signal quality loss accumulated through the bypass circuitry between empty slots. Empty backplanes can generate errors which are intermittent and difficult to isolate. As disks are added they should be spaced to minimize the gaps between disks.
Incorrect screen size

stty rows 24
stty cols 80

Too many open files

The default value for maximum number of files open in Solaris 2.5.1 is 64 - this can be checked with ulimit -n. To set this to a higher default value in 2.5.1, add the following to /etc/system

set rlim_fd_max= #(NOT greater then 1024)
set rlim_fd_cur=

and reboot the system.

To set the value for one user or session;

ulimit #(NOT greater then 1024)

Installing Disks

* shut down the system (init 0)
* plug in the new disks, ensuring no duplicate scsi numbers within a controller. This can be checked with a probe-scsi-all
* do a reconfigure boot (boot -r)

If disks are added and the system is booted without a reconfigure, these can be "seen" by running drvconfig ensures the /devices tree is up to date and correct

disks creates the symbolic links to /devices in /dev/[r]dsk

tapes creates the symbolic links to /devices in /dev/[r]mt
Reading utmp and wtmp
/usr/bin/last converts /var/adm/wtmpx to readable data. cat /var/adm/utmp | /usr/lib/acct/fwtmp > /tmp/utmp.ascii can be used to make utmp readable.
swapfile

To add additional (temporary) swap, can create a filesystem swap file

# mkfile 32M /u/swapfile
# swap -a /u/swapfile

add a line like the following to /etc/vfstab to make it permanent

/u/swapfile - - swap - no -

kernel drivers

To find out modules are currently loaded into the kernel:

# modinfo

Id Loadaddr Size Info Rev Module Name
5 600fa000 3b30 1 1 specfs (filesystem for specfs)
7 6011f000 2bc8 1 1 TS (time sharing sched class)
8 600f0a88 4a4 - 1 TS_DPTBL (Time sharing dispatch table)
9 60142000 234b8 2 1 ufs (filesystem for ufs)
10 6017c000 dc4b 226 1 rpcmod (RPC syscall)
10 6017c000 dc4b 1 1 rpcmod (rpc interface str mod)
11 60196000 277ef 0 1 ip (IP Streams module)
11 60196000 277ef 3 1 ip (IP Streams device)
12 60123550 127f 1 1 rootnex (sun4u root nexus)
. . .

The first field of output is an identifier. It is possible to unload a module from the kernel using that number. This will fail if the driver is busy.

# modunload -i 23

To load a module

# cd /kernel/drv #(or wherever it lives e.g. /usr/kernel/drv )
# modload st

To unload the st driver

The st driver is used to control tape drives. If a tape drive definition has changed, the driver needs to be reloaded before it will use the new definitions. It is possible to manually load it as show above, but it will be autoloaded as soon as atape drive is used. Make sure none of your tape drives are in use:

# for tape in /dev/rmt/?
> do
> mt -f $tape rewind
> done
#

If you get an error like "/dev/rmt/0: no tape loaded or drive offline" don't worry it just means no tapes are loaded and therefore the device can't be in use.
Remote root login
It is, of course, a bad idea to allow network logins as root all the time but it can be extremely useful during initial install once you've got the network up. Edit /etc/default/login and comment out the following line to allow remote login by root.

CONSOLE=/dev/console

Remember to uncomment it when you're done

Network Printers
These days, most printers which are going to be accessed from a Sun box will already be set up and working on the office network. They will already have a name defined in DNS and/or a well known IP address. This can be added to /etc/hosts if required. Once you know where it is, you need to tell the print service as follows:

lpadmin -p printername -s printername

If the printer is not directly on the network but can be accessed via a defined print server, you can use the following form:

lpadmin -p printername -s print_server!printername

To make a printer the default for the server:

lpadmin -d printername

Pretty printing
A sub-topic for setting up printing is to actually print nicely. Desktop-oriented printers probably aren't going to cope well with unix style files but it is possible to get around this using a the 'mp' print pre-processor. The simplest example is:

mp filename | lpr

Or

filep -l -h filename
# -l for landscape format, -h no header page

Look at the man page for more tips and tricks.
makewhatis
What do you do when you get annoying messages like

/usr/man/windex: No such file or directory

when you try a to use man -k (also known as apropos) ?

You need to find and use makewhatis to make your index.

Patching
However much - or little - patching you do, knowing the patch return codes is very useful. The most 'ignorable' codes are 2 (patch already applied) and 8 (attempt to patch a non-installed package). For a complete list, have a look here.

Courthney's Aching eye

2009-02-20T06:09:00.003+08:00

Today, Courthney always complain about her aching eyes. So me and my wife is thinking that maybe she need a glasses.

Fish...

2009-02-18T11:19:00.004+08:00

Last week my wife bought a set of aquarium (the 50RM worth). Yesterday the last fish died. My kids seems not to be bothered but Alex (my second) ask me what should we do those fish. I do not know what to tell her, I just said we need to bury them..

US Visa interview Experience

2009-02-17T12:22:00.005+08:00

Today we went to US embassy for a tourist visa interview for family. We arrived at the embassy at around 9:30am, our scheduled as stated on our appointment was 10am.

After sometimes queuing and verification at the embassy gate we were allowed to enter the embassy premises. We were then ask to wait at the waiting area. My wife and I anxiously waited for our number to be called while we hear other people being interviewed by the consul. This make me nervous since I heard that some are being denied. My wife noticed that on window number 3 the consul always approved the visa. We are hoping to be interviewed by that consul for that reason.

When our number was called (A101 is our number), We ask to proceed on Window #3. I think we were lucky to be called by the same consul who is on window 3. During the interview, the consul only asked for my monthly salary and the nature of my work and look for my employment letter. After less than 2 minutes chatting with the consul she told us our visa is approved, and wish us good trip. She then gave us instruction on how to pickup our passport the next day.

I think my wife and I are lucky today.

Alex and Mica

2009-02-15T02:44:00.003+08:00

Feb 14, 2009

2009-02-15T00:02:00.002+08:00

I dated four girls this Valentines day. I bring my girls to a park nearby our condo to celebrate the day of the hearts.

Lucky me!

Suprise for the Kids

2009-02-13T11:23:00.005+08:00

Today when my wife arrives from PUDU market to buy our weekly supply of foods, she bring along an aquarium with 2 gold fish and 2 Koi (I'm not sure if its really a koi).

After the mini aquarium was setup my youngest Mica was really amazed of the fish and always wanted to stay besides the aquarium. I wonder what will be the reaction of my two other daughters when they see the aquarium. One thing for sure they will be surprise!

For 50 Ringit worth, I know my wife's decision to buy the aquarium will dividend a big smile to my kids that money can not buy.

Solaris: pkgadd: ERROR: checkinstall error Solution

2009-02-12T15:37:00.003+08:00

root@mike# pkgadd -d ./TIVsmCapi.pkg

The following packages are available:
1 TIVsmCapi IBM Tivoli Storage Manager Solaris 9/10 API Client
(sparc) Version 5 Release 5 Level 0.0

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: all

Processing package instance from

IBM Tivoli Storage Manager Solaris 9/10 API Client
(sparc) Version 5 Release 5 Level 0.0
Licensed Materials - Property of IBM

5655-A30
(C) Copyright International Business Machines Corp. 1990, 2007.

All rights reserved.
US Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.

## Executing checkinstall script.
/var/tmp/dstreAAAuhaOTF/TIVsmCapi/install/checkinstall: /var/tmp/dstreAAAuhaOTF/TIVsmCapi/install/checkinstall: cannot open
pkgadd: ERROR: checkinstall script did not complete successfully

I found the solution from the net below with Solaris FAQ:

The solaris FAQ says:

5.53) Patch installation often fails with "checkinstall" errors.

When installing a patch, the Solaris 2.5+ patch installation procedure will execute the script "checkinstall" with uid nobody.

If any of the patch files cannot be read by nobody or if any part of the path leading up to the patch directory an error similar to the following will appear:

./installpatch . Generating list of files to be patched... Verifying sufficient filesystem capacity (exhaustive method) ... Installing patch packages... pkgadd: ERROR: checkinstall script did not complete successfully ....

You can workaround this in two ways, one is to make sure that nobody can read all patch files and execute a "pwd" in the patch directory or add an account "install" to /etc/passwd:

install:x:0:1:installpatch braindamage:/:/bin/true

Installpatch uses "nobody" as a fallback if it cannot find the "install" user.

Linux Ethernet Bonding mini howto

2009-02-10T10:17:00.002+08:00

Linux Ethernet Bonding Driver mini-howto

------
The bonding driver originally came from Donald Becker's beowulf patches for
kernel 2.0. It has changed quite a bit since, and the original tools from
extreme-linux and beowulf sites will not work with this version of the driver.

For new versions of the driver, patches for older kernels and the updated
userspace tools, please follow the links at the end of this file.

Installation
============

1) Build kernel with the bonding driver
---------------------------------------
For the latest version of the bonding driver, use kernel 2.4.12 or above
(otherwise you will need to apply a patch).

Configure kernel with `make menuconfig/xconfig/config', and select
"Bonding driver support" in the "Network device support" section. It is
recommended to configure the driver as module since it is currently the only way
to pass parameters to the driver and configure more than one bonding device.

Build and install the new kernel and modules.

2) Get and install the userspace tools
--------------------------------------
This version of the bonding driver requires updated ifenslave program. The
original one from extreme-linux and beowulf will not work. Kernels 2.4.12
and above include the updated version of ifenslave.c in Documentation/network
directory. For older kernels, please follow the links at the end of this file.

IMPORTANT!!! If you are running on Redhat 7.1 or greater, you need
to be careful because /usr/include/linux is no longer a symbolic link
to /usr/src/linux/include/linux. If you build ifenslave while this is
true, ifenslave will appear to succeed but your bond won't work. The purpose
of the -I option on the ifenslave compile line is to make sure it uses
/usr/src/linux/include/linux/if_bonding.h instead of the version from
/usr/include/linux.

To install ifenslave.c, do:
# gcc -Wall -Wstrict-prototypes -O -I/usr/src/linux/include ifenslave.c -o ifenslave
# cp ifenslave /sbin/ifenslave

3) Configure your system
------------------------
Also see the following section on the module parameters. You will need to add
at least the following line to /etc/conf.modules (or /etc/modules.conf):

alias bond0 bonding

Use standard distribution techniques to define bond0 network interface. For
example, on modern RedHat distributions, create ifcfg-bond0 file in
/etc/sysconfig/network-scripts directory that looks like this:

DEVICE=bond0
IPADDR=192.168.1.1
NETMASK=255.255.255.0
NETWORK=192.168.1.0
BROADCAST=192.168.1.255
ONBOOT=yes
BOOTPROTO=none
USERCTL=no

(put the appropriate values for you network instead of 192.168.1).

All interfaces that are part of the trunk, should have SLAVE and MASTER
definitions. For example, in the case of RedHat, if you wish to make eth0 and
eth1 (or other interfaces) a part of the bonding interface bond0, their config
files (ifcfg-eth0, ifcfg-eth1, etc.) should look like this:

DEVICE=eth0
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none

(use DEVICE=eth1 for eth1 and MASTER=bond1 for bond1 if you have configured
second bonding interface).

Restart the networking subsystem or just bring up the bonding device if your
administration tools allow it. Otherwise, reboot. (For the case of RedHat
distros, you can do `ifup bond0' or `/etc/rc.d/init.d/network restart'.)

If the administration tools of your distribution do not support master/slave
notation in configuration of network interfaces, you will need to configure
the bonding device with the following commands manually:

# /sbin/ifconfig bond0 192.168.1.1 up
# /sbin/ifenslave bond0 eth0
# /sbin/ifenslave bond0 eth1

(substitute 192.168.1.1 with your IP address and add custom network and custom
netmask to the arguments of ifconfig if required).

You can then create a script with these commands and put it into the appropriate
rc directory.

If you specifically need that all your network drivers are loaded before the
bonding driver, use one of modutils' powerful features : in your modules.conf,
tell that when asked for bond0, modprobe should first load all your interfaces :

probeall bond0 eth0 eth1 bonding

Be careful not to reference bond0 itself at the end of the line, or modprobe will
die in an endless recursive loop.

4) Module parameters.
---------------------
The following module parameters can be passed:

mode=

Possible values are 0 (round robin policy, default) and 1 (active backup
policy), and 2 (XOR). See question 9 and the HA section for additional info.

miimon=

Use integer value for the frequency (in ms) of MII link monitoring. Zero value
is default and means the link monitoring will be disabled. A good value is 100
if you wish to use link monitoring. See HA section for additional info.

downdelay=

Use integer value for delaying disabling a link by this number (in ms) after
the link failure has been detected. Must be a multiple of miimon. Default
value is zero. See HA section for additional info.

updelay=

Use integer value for delaying enabling a link by this number (in ms) after
the "link up" status has been detected. Must be a multiple of miimon. Default
value is zero. See HA section for additional info.

arp_interval=

Use integer value for the frequency (in ms) of arp monitoring. Zero value
is default and means the arp monitoring will be disabled. See HA section
for additional info. This field is value in active_backup mode only.

arp_ip_target=

An ip address to use when arp_interval is > 0. This is the target of the
arp request sent to determine the health of the link to the target.
Specify this value in ddd.ddd.ddd.ddd format.

If you need to configure several bonding devices, the driver must be loaded
several times. I.e. for two bonding devices, your /etc/conf.modules must look
like this:

alias bond0 bonding
alias bond1 bonding

options bond0 miimon=100
options bond1 -o bonding1 miimon=100

5) Testing configuration
------------------------
You can test the configuration and transmit policy with ifconfig. For example,
for round robin policy, you should get something like this:

[root]# /sbin/ifconfig
bond0 Link encap:Ethernet HWaddr 00:C0:F0:1F:37:B4
inet addr:XXX.XXX.XXX.YYY Bcast:XXX.XXX.XXX.255 Mask:255.255.252.0
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:7224794 errors:0 dropped:0 overruns:0 frame:0
TX packets:3286647 errors:1 dropped:0 overruns:1 carrier:0
collisions:0 txqueuelen:0

eth0 Link encap:Ethernet HWaddr 00:C0:F0:1F:37:B4
inet addr:XXX.XXX.XXX.YYY Bcast:XXX.XXX.XXX.255 Mask:255.255.252.0
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:3573025 errors:0 dropped:0 overruns:0 frame:0
TX packets:1643167 errors:1 dropped:0 overruns:1 carrier:0
collisions:0 txqueuelen:100
Interrupt:10 Base address:0x1080

eth1 Link encap:Ethernet HWaddr 00:C0:F0:1F:37:B4
inet addr:XXX.XXX.XXX.YYY Bcast:XXX.XXX.XXX.255 Mask:255.255.252.0
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:3651769 errors:0 dropped:0 overruns:0 frame:0
TX packets:1643480 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:9 Base address:0x1400

Questions :
===========

1. Is it SMP safe?

Yes. The old 2.0.xx channel bonding patch was not SMP safe.
The new driver was designed to be SMP safe from the start.

2. What type of cards will work with it?

Any Ethernet type cards (you can even mix cards - a Intel
EtherExpress PRO/100 and a 3com 3c905b, for example).
You can even bond together Gigabit Ethernet cards!

3. How many bonding devices can I have?

One for each module you load. See section on module parameters for how
to accomplish this.

4. How many slaves can a bonding device have?

Limited by the number of network interfaces Linux supports and the
number of cards you can place in your system.

5. What happens when a slave link dies?

If your ethernet cards support MII status monitoring and the MII
monitoring has been enabled in the driver (see description of module
parameters), there will be no adverse consequences. This release
of the bonding driver knows how to get the MII information and
enables or disables its slaves according to their link status.
See section on HA for additional information.

For ethernet cards not supporting MII status, or if you wish to
verify that packets have been both send and received, you may
configure the arp_interval and arp_ip_target. If packets have
not been sent or received during this interval, an arp request
is sent to the target to generate send and receive traffic.
If after this interval, either the successful send and/or
receive count has not incremented, the next slave in the sequence
will become the active slave.

If neither mii_monitor and arp_interval is configured, the bonding
driver will not handle this situation very well. The driver will
continue to send packets but some packets will be lost. Retransmits
will cause serious degradation of performance (in the case when one
of two slave links fails, 50% packets will be lost, which is a serious
problem for both TCP and UDP).

6. Can bonding be used for High Availability?

Yes, if you use MII monitoring and ALL your cards support MII link
status reporting. See section on HA for more information.

7. Which switches/systems does it work with?

In round-robin mode, it works with systems that support trunking:

* Cisco 5500 series (look for EtherChannel support).
* SunTrunking software.
* Alteon AceDirector switches / WebOS (use Trunks).
* BayStack Switches (trunks must be explicitly configured). Stackable
models (450) can define trunks between ports on different physical
units.
* Linux bonding, of course !

In Active-backup mode, it should work with any Layer-II switches.

8. Where does a bonding device get its MAC address from?

If not explicitly configured with ifconfig, the MAC address of the
bonding device is taken from its first slave device. This MAC address
is then passed to all following slaves and remains persistent (even if
the the first slave is removed) until the bonding device is brought
down or reconfigured.

If you wish to change the MAC address, you can set it with ifconfig:

# ifconfig bond0 ha ether 00:11:22:33:44:55

The MAC address can be also changed by bringing down/up the device
and then changing its slaves (or their order):

# ifconfig bond0 down ; modprobe -r bonding
# ifconfig bond0 .... up
# ifenslave bond0 eth...

This method will automatically take the address from the next slave
that will be added.

To restore your slaves' MAC addresses, you need to detach them
from the bond (`ifenslave -d bond0 eth0'), set them down
(`ifconfig eth0 down'), unload the drivers (`rmmod 3c59x', for
example) and reload them to get the MAC addresses from their
eeproms. If the driver is shared by several devices, you need
to turn them all down. Another solution is to look for the MAC
address at boot time (dmesg or tail /var/log/messages) and to
reset it by hand with ifconfig :

# ifconfig eth0 down
# ifconfig eth0 hw ether 00:20:40:60:80:A0

9. Which transmit polices can be used?

Round robin, based on the order of enslaving, the output device
is selected base on the next available slave. Regardless of
the source and/or destination of the packet.

XOR, based on (src hw addr XOR dst hw addr) % slave cnt. This
selects the same slave for each destination hw address.

Active-backup policy that ensures that one and only one device will
transmit at any given moment. Active-backup policy is useful for
implementing high availability solutions using two hubs (see
section on HA).

High availability
=================

To implement high availability using the bonding driver, you need to
compile the driver as module because currently it is the only way to pass
parameters to the driver. This may change in the future.

High availability is achieved by using MII status reporting. You need to
verify that all your interfaces support MII link status reporting. On Linux
kernel 2.2.17, all the 100 Mbps capable drivers and yellowfin gigabit driver
support it. If your system has an interface that does not support MII status
reporting, a failure of its link will not be detected!

The bonding driver can regularly check all its slaves links by checking the
MII status registers. The check interval is specified by the module argument
"miimon" (MII monitoring). It takes an integer that represents the
checking time in milliseconds. It should not come to close to (1000/HZ)
(10 ms on i386) because it may then reduce the system interactivity. 100 ms
seems to be a good value. It means that a dead link will be detected at most
100 ms after it goes down.

Example:

# modprobe bonding miimon=100

Or, put in your /etc/modules.conf :

alias bond0 bonding
options bond0 miimon=100

There are currently two policies for high availability, depending on whether
a) hosts are connected to a single host or switch that support trunking
b) hosts are connected to several different switches or a single switch that
does not support trunking.

1) HA on a single switch or host - load balancing
-------------------------------------------------
It is the easiest to set up and to understand. Simply configure the
remote equipment (host or switch) to aggregate traffic over several
ports (Trunk, EtherChannel, etc.) and configure the bonding interfaces.
If the module has been loaded with the proper MII option, it will work
automatically. You can then try to remove and restore different links
and see in your logs what the driver detects. When testing, you may
encounter problems on some buggy switches that disable the trunk for a
long time if all ports in a trunk go down. This is not Linux, but really
the switch (reboot it to ensure).

Example 1 : host to host at double speed

+----------+ +----------+
| |eth0 eth0| |
| Host A +--------------------------+ Host B |
| +--------------------------+ |
| |eth1 eth1| |
+----------+ +----------+

On each host :
# modprobe bonding miimon=100
# ifconfig bond0 addr
# ifenslave bond0 eth0 eth1

Example 2 : host to switch at double speed

+----------+ +----------+
| |eth0 port1| |
| Host A +--------------------------+ switch |
| +--------------------------+ |
| |eth1 port2| |
+----------+ +----------+

On host A : On the switch :
# modprobe bonding miimon=100 # set up a trunk on port1
# ifconfig bond0 addr and port2
# ifenslave bond0 eth0 eth1

2) HA on two or more switches (or a single switch without trunking support)
---------------------------------------------------------------------------
This mode is more problematic because it relies on the fact that there
are multiple ports and the host's MAC address should be visible on one
port only to avoid confusing the switches.

If you need to know which interface is the active one, and which ones are
backup, use ifconfig. All backup interfaces have the NOARP flag set.

To use this mode, pass "mode=1" to the module at load time :

# modprobe bonding miimon=100 mode=1

Or, put in your /etc/modules.conf :

alias bond0 bonding
options bond0 miimon=100 mode=1

Example 1: Using multiple host and multiple switches to build a "no single
point of failure" solution.

| |
|port3 port3|
+-----+----+ +-----+----+
| |port7 ISL port7| |
| switch A +--------------------------+ switch B |
| +--------------------------+ |
| |port8 port8| |
+----++----+ +-----++---+
port2||port1 port1||port2
|| +-------+ ||
|+-------------+ host1 +---------------+|
| eth0 +-------+ eth1 |
| |
| +-------+ |
+--------------+ host2 +----------------+
eth0 +-------+ eth1

In this configuration, there are an ISL - Inter Switch Link (could be a trunk),
several servers (host1, host2 ...) attached to both switches each, and one or
more ports to the outside world (port3...). One an only one slave on each host
is active at a time, while all links are still monitored (the system can
detect a failure of active and backup links).

Each time a host changes its active interface, it sticks to the new one until
it goes down. In this example, the hosts are not too much affected by the
expiration time of the switches' forwarding tables.

If host1 and host2 have the same functionality and are used in load balancing
by another external mechanism, it is good to have host1's active interface
connected to one switch and host2's to the other. Such system will survive
a failure of a single host, cable, or switch. The worst thing that may happen
in the case of a switch failure is that half of the hosts will be temporarily
unreachable until the other switch expires its tables.

Example 2: Using multiple ethernet cards connected to a switch to configure
NIC failover (switch is not required to support trunking).

+----------+ +----------+
| |eth0 port1| |
| Host A +--------------------------+ switch |
| +--------------------------+ |
| |eth1 port2| |
+----------+ +----------+

On host A : On the switch :
# modprobe bonding miimon=100 mode=1 # (optional) minimize the time
# ifconfig bond0 addr # for table expiration
# ifenslave bond0 eth0 eth1

Each time the host changes its active interface, it sticks to the new one until
it goes down. In this example, the host is strongly affected by the expiration
time of the switch forwarding table.

3) Adapting to your switches' timing
------------------------------------
If your switches take a long time to go into backup mode, it may be
desirable not to activate a backup interface immediately after a link goes
down. It is possible to delay the moment at which a link will be
completely disabled by passing the module parameter "downdelay" (in
milliseconds, must be a multiple of miimon).

When a switch reboots, it is possible that its ports report "link up" status
before they become usable. This could fool a bond device by causing it to
use some ports that are not ready yet. It is possible to delay the moment at
which an active link will be reused by passing the module parameter "updelay"
(in milliseconds, must be a multiple of miimon).

A similar situation can occur when a host re-negotiates a lost link with the
switch (a case of cable replacement).

A special case is when a bonding interface has lost all slave links. Then the
driver will immediately reuse the first link that goes up, even if updelay
parameter was specified. (If there are slave interfaces in the "updelay" state,
the interface that first went into that state will be immediately reused.) This
allows to reduce down-time if the value of updelay has been overestimated.

Examples :

# modprobe bonding miimon=100 mode=1 downdelay=2000 updelay=5000
# modprobe bonding miimon=100 mode=0 downdelay=0 updelay=5000

4) Limitations
--------------
The main limitations are :
- only the link status is monitored. If the switch on the other side is
partially down (e.g. doesn't forward anymore, but the link is OK), the link
won't be disabled. Another way to check for a dead link could be to count
incoming frames on a heavily loaded host. This is not applicable to small
servers, but may be useful when the front switches send multicast
information on their links (e.g. VRRP), or even health-check the servers.
Use the arp_interval/arp_ip_target parameters to count incoming/outgoing
frames.

Resources and links
===================

Current development on this driver is posted to:
- http://www.sourceforge.net/projects/bonding/

Donald Becker's Ethernet Drivers and diag programs may be found at :
- http://www.scyld.com/network/

You will also find a lot of information regarding Ethernet, NWay, MII, etc. at
www.scyld.com.

For new versions of the driver, patches for older kernels and the updated
userspace tools, take a look at Willy Tarreau's site :
- http://wtarreau.free.fr/pub/bonding/
- http://www-miaif.lip6.fr/willy/pub/bonding/

To get latest informations about Linux Kernel development, please consult
the Linux Kernel Mailing List Archives at :
http://boudicca.tux.org/hypermail/linux-kernel/latest/

-- END --

SMI/EFI disk howto change the label

2009-02-05T05:23:00.004+08:00

I am changing the disk on Sol 10 server Sun-Fire-V245 when I encounter a problem after I used the usual prtvtoc and fmthard command to copy the desired partition table on the new disk. Below is the error:

root@houic-u-s00019 # prtvtoc /dev/rdsk/c1t9d0s2 | fmthard -s - /dev/rdsk/c1t12d0s2
*Partition 0 not aligned on cylinder boundary: " 0 4 00 34 143358287 143358320"*

I did inform the Synstar Engineer about the issue and he then mentioned that the disk they have just installed has an SMI Label. Below I give the example on how to spot the difference between the SMI and EFI labelled disk. Notice that SMI used cylinders while EFI used sectors. Also notice that SMI uses 8 slices; numbered 0-7 with slice 2 being the whole disk.

SMI Labelled Disk:

partition> p
Current partition table (unnamed):
Total disk cylinders available: 14087 + 2 (reserved cylinders)

Part Tag Flag Cylinders Size Blocks
0 usr wm 0 - 11615 56.36GB (11616/0/0) 118204416
1 unassigned wm 0 0 (0/0/0) 0
2 unassigned wm 0 0 (0/0/0) 0
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0

partition>

EFI Labelled Disk:

partition> p
Current partition table (original):
Total disk sectors available: 143358320 + 16384 (reserved sectors)

Part Tag Flag First Sector Size Last Sector
0 unassigned wm 0 0 0
1 unassigned wm 0 0 0
2 unassigned wm 0 0 0
3 unassigned wm 0 0 0
4 unassigned wm 0 0 0
5 unassigned wm 0 0 0
6 unassigned wm 0 0 0
8 reserved wm 143358320 8.00MB 143374703

partition>

Below is the steps on how to change the Disk label from SMI to EFI.

1. Use format in expert mode: format -e

2. Then select the target disk.

3. Finaly inside format use label to change the disk label. Select 1. Voila! your disk label is now EFI.

4. Dont forget to verify the partition table using format.

root@houic-u-s00019 # format -e

Searching for disks...done

AVAILABLE DISK SELECTIONS:
8. c1t12d0
/pci@1f,700000/pci@0/scsi@2/sd@c,0
9. c1t13d0
/pci@1f,700000/pci@0/scsi@2/sd@d,0
Specify disk (enter its number): 8
selecting c1t12d0
[disk formatted]

----

format> label
[0] SMI Label
[1] EFI Label
Specify Label type[0]: 1
Warning: This disk has an SMI label. Changing to EFI label will erase all
current partitions.
Continue? y
format>

================================================================

Digging deep into the difference between SMI and EFI, I found the info below:

The advantage of the EFI label is that it supports LUNs over 1TB in size and prevents overlapping partitions by providing a whole-disk device called cxtydz rather than using cxtydzs2. Site below also explain further EFI advantage over SMI.

http://docsun.cites.uiuc.edu/sun_docs/C/solaris_9/SUNWaadm/SYSADV1/p117.html

Solaris soltice Mini howto I shared with my group

2009-02-05T03:34:00.001+08:00

Just want to share the mini howto I prepared in case you encounter an e-change to replace the defective disk on Solaris machine using Solaris volume manager.

Please ignore this howto if you already master the other way of changing the disk on solaris machines :D. Comments to improve this howto are very much welcome.

1) Run 'metadetach' to detach all submirrors on the failing disk from their respective mirrors, and then run 'metaclear' (**) on those submirror devices (see below). if you don't use -f option you will get the following message : "Attempt an operation on a submirror that has erred component"

In sample case the failed disk is c1t0d0

metadetach d0 d10
metadetach d1 d11
metaclear d10
metaclear d11

You can verify there are no existing metadevices left on the disk by
running '
metastat -p | grep c1t0d0

2.Next step is to remove the replicas on this disk c1t0d0
To view the replicas on this disk
$ metadb |grep c1t0d0

Wm p l 16 8192 /dev/dsk/c1t0d0s7
W p l 8208 8192 /dev/dsk/c1t0d0s7

If there are any replicas on this disk, remove them using

metadb -d c1t0d0s7

You can verify there are no existing replicas left on the disk by
running
metadb | grep c1t0d0

3. If there are any open filesystems on this disk (not under SVM control), unmount them.

4. Run the 'cfgadm' command to remove the failed disk.

cfgadm -c unconfigure c1::dsk/c1t0d0

5. Insert and configure in the new disk. Make sure the disk was inserted on the same location where the failed disk was pull-out.

cfgadm -cc configure c1::dsk/c1t0d0
cfgadm -al

Then try to run format to re verify if the OS already recognize the new disk

6. Run 'format' or 'prtvtoc' to put the desired partition table on the new disk .
Note : The VTOC (volume table of contents) on the root disk and root mirror must be the same. Copy the VTOC using prtvtoc and fmthard.
$ prtvtoc /dev/rdsk/c1t1d0s2 | fmthard -s - /dev/rdsk/c1t0d0s2

7. If necessary, recreate any replicas on the new disk:
metadb -a -c 3 c1t0d0s7

8. Recreate each metadevice to be used as submirrors, and use 'metattach' to attach those submirrors to the mirrors to start the resync. Note: If the submirror was something other than a simple one-slice concat device, the metainit command will be different than shown here.
metainit 1 1
metattach

metainit d10 1 1 c1t0d0s0
metattach d0 d10
metainit d11 1 1 c1t0d0s1
metattach d1 d11

Solaris 10 thingy trunking/aggregation

2009-02-05T03:32:00.001+08:00

Recently, I was looking for information on what Ethernet cards will work with Nemo drivers for link aggregation/trunking. It was a long search and took me a while to figure out what is supported and what product/technologies should be used on what hardware. So, here are my notes for configuring trunking on various Solaris 10 systems.

The first thing you should do before even begin working on trunking on a Solaris 10 machine is to make sure it has latest patches.

Next, check what kind of Ethernet driver do you have. There are several ways you can find out. Here is one way:

dladm show-link

Look for the first word for each line. If you see any of the following driver types, then you can use Nemo drivers: bge, e1000g, xge, nge, rge, ixgb

If you have qfe, ge, or ce, then you should use Sun Trunking 1.3. See also support matrix.

Let’s say that you have Nemo supported drivers, then here are the steps to setup link aggregation:

1. Identify which ports you want to aggregate. dladm show-link should give you an idea what are available. I’ll assume you want to aggregate bge0 and bge1.
2. Run the following command to create an aggregation interface:

dladm create-aggr -d bge0 -d bge1 1

If you get an error, it is most likly you either attempting to use Nemo drivers on a not supported Ethernet driver or you do not have the latest patches for Solaris 10.
3. Plumb the interface. See example below:

ifconfig aggr1 plub 192.168.1.200 up

4. Check the configuration:

dladm show-aggr
ifconfig -a

If you decided that Sun Trunking 1.3 is what you need, then follow the steps below:

1. Download the binary.
2. Read the Installation Guide
3. After unzip the binary from step #1, follow the installation steps stated in page 46 (printed on the left corner on the page or page 56 according to your Acrobat reader) in the Installation guide.
4. Install the appripriate patches for the driver you use. See page 44 (printed on the page or 54 according to Acrobat reader) in the Installation Guide.
5. Set local-mac-address as root on the command-line:

eeprom local-mac-address?=true

6.Reboot
7. Make sure the interfacs that you want aggregate isn’t plumb. If not, use the following command to unplumb:

ifconfig ce0 unplumb

8 Create an aggregated interface

/etc/opt/SUNWconn/bin/nettr -setup 0 device ce  members=0,1

This should create an aggregated interface for use with switches (MAC based policy) If you want to use Round Robin for back to back connection, use the following command instead:

/etc/opt/SUNWconn/bin/nettr -setup 0 device ce members=0,1 policy=2

See Page 29 and 32 for further information about other policies.
9. Plumb the interface.

ifconfig ce0 plumb 192.168.1.200 up

10. Check config:

/etc/opt/SUNWconn/bin/nettr -conf

2009-01-09T08:14:00.003+08:00

Collage

2008-09-29T20:16:00.002+08:00

Wedding Pictures

Pictures of my family after 6 years

2008-09-29T18:50:00.001+08:00

Pictures taken during our church weeding. My wife and I decided to have our church weeding just before we migrate to Malaysia. This church wedding was held at Sto. Nino Parish Church at Pandacan on 8:00AM of 08/08/08. This date happened to be our civil wedding 6 years aniversary also :).

I take the Shell Offer!

2008-01-23T01:13:00.000+08:00

Question is "Should I take the offer or leave it?"

I come to think about it. Only few has given a chance to be a Shell Staff. Also, Shell is a stable company and the benefits are as good as you can get on other big companies. Besides that Shell offers a lot of exposures on different OS and not to mentioned free trainings. So today I decided to take the offer. Syempre may dagdag kasi nag negotiate ako :)

( Shell offer) To take it or leave it..

2008-01-21T11:39:00.000+08:00

Last week I received an email from my hiring manager, In that email he congratulated me and told me that I pass the medical exam and the though assessment. I am eligible to be a shell staff and they are offering me a new salary scheme.

Upon seeing the said offer, I was shocked! its not acceptable! Shell's offer is not good. Damn low! All my excitement gone in to whirl wind. I can not accept the offer that comes into my mind. I lost a big amount from my salary while I am a TPC!

I tried to talk to my hiring manager but he told me that's what he can offer equivalent to my work experience.

Currently I am still negotiating for the "ideal salary" so that me and my family can survive here in KL.

I really want to take the oppurtunity to become a Shell staff but I am also thinking of the salary that they offer to me.

As I said, I am thinking whats the best for my family. Im confused now.

Simeona Michaela

2008-01-21T11:30:00.000+08:00

My third baby is a girl! I only seen my baby on the pictures because I am here in Malaysia working. I've been wanting to see my new born kid since my wife gave birth but my work here wont allow me.

But on Feb 2nd week I will be back to see her.

Fishing Expidition (Kajang, Malaysia)

2007-07-19T15:31:00.000+08:00

This picture was taken during my first Fishing expedition here in Malaysia.. This is actually my first time do use a fishing rod :) I'm used of using bamboo stick when i was a kid. Thanks to my new Malay Friends Mota, Akhmal and Arifah.

akin po chicken joy din!

2007-07-17T08:47:00.000+08:00

"Akin po chicken joy din" The favorite expression of Alex always making sure that what Ate Courthney wants Baby Alex must have also. This picture was taken during the usual family day me and my wife make sure every week to spend some quality time with our kids. The day usually starts by eating breakfast on Jollibee or Mcdo. After eating we go to places were Ate and Alex can enjoy and learn different things.

I miss those days spending time with my wife and kids.

Our Lola Tolya

2007-07-16T14:14:00.001+08:00

This is our Lola Tolya, she is already 97 years old. At her age she is strong, she claims that she is even feeling stronger since Courthney and Alex is now in our house. She is a bit ulyanin but still remember all her apo by just recognizing our voice. I love my lola, I remember sleeping on her room whenever i need to learn prayers.

Right now, she was not able to go to church as what she did before, so instead of her going to the church, the priest visited my lola once a week for her prayers.

The next Calizo is a BOY!!!

2007-07-16T12:50:00.000+08:00

Today 12:05pm, My wife gave me a good news… The result of her recent ultrasound reveals that the baby she is carrying for 6 months now is a BOY. I am so ecstatic to hear that good news from my wife. Finally it’s a BOY!! It’s been a long wait especially for me just to get to know the sex of the baby my wife is carrying on her womb. I have been waiting for a baby boy since my two kids were both girls.

Now that I know that my third child is a boy, the 1^st thing comes into my mind is if I make him my Junior. My wife suggested naming him Simon Michael. As of the moment its not yet decided. The second thing that comes into my mind is the toys that I am going to buy J so that I can play also. Now I can buy my childhood dream toys and my wife will not question why I bought it.

At the Antipolo church

2007-07-16T12:26:00.000+08:00

Unang Simba sa antipolo ni Courthney and Alex.
Kasama si Mama at papa(wala sa pic kasi tagakuha ng pic)

during my first shooting..

2007-07-15T14:49:00.000+08:00

Shots Taken by HAYA.

Ponce the Dog

2007-07-15T14:03:00.000+08:00

This is my mini Pincher dog. I call him Ponce.

My Study Table.

2007-07-15T12:06:00.000+08:00

Just sharing this... Ill be sitting here whole day during my off shift.

Thats how I spend my day being far from my beloved family....

The Source of my strength....

2007-07-15T00:22:00.000+08:00

My wife Beth, Ate Courthney and Alex kulit.

Ganda ng mga chicks ko. :)

Taking Shots.

2007-07-14T23:45:00.001+08:00

Using d50 dslr on smooking area of Shell Office

Shell Office..

2007-07-14T23:41:00.001+08:00

dito ako nakaupo.

In the Shell Office

2007-07-14T22:42:00.000+08:00

Taking picture. At the back is my friend Mota.

In the Shell Office

2007-07-14T22:38:00.000+08:00

Working night shift.. Kidding around with friends.

Using Hacked AP..

2007-07-14T11:11:00.000+08:00

Libre Internet ko dito sa Cyberjaya..

2007-07-14T10:53:00.000+08:00

Stairway to.....

I like this picture..

the looks... wala lang

2007-07-14T10:46:00.000+08:00

The photographer in me...

Sa Bus..

2007-07-14T10:28:00.001+08:00

Pauwi galing sa night shift na work.

sa Bahay nila Alvin

2007-07-14T10:19:00.000+08:00

Bisita sa bahay nila Pare ALvin.. Kasama ko mga HP boys. Ito ang unang inoman ko sa Malaysia..

Relaxing with my housemates.

2007-07-14T10:16:00.000+08:00

Appartment in CyberJaya-kusina

2007-07-14T10:11:00.001+08:00

Appartment in CyberJaya-View

2007-07-14T10:07:00.001+08:00

The View. I am staying on the 6th floor.

Appartment in CyberJaya-room

2007-07-14T10:03:00.000+08:00

This is my room...

Appartment in CyberJaya

2007-07-14T09:52:00.000+08:00

This is the Sala.. No TV :)

The Twin towers

2007-07-14T09:27:00.000+08:00

I have a chance to go around KL. And for me this is the best sight that you can see so far since i'm quite new here. The KL twintowers.

My Adventure in Malaysia

2007-07-14T09:13:00.000+08:00

I Arrived here in Malaysia May 7, 2007 at KLIA(KL International Airport) around 10pm. We were 3 Filipinos. We were then sent to a Hostel named YMCA-KL. It was about 1 1/2 hours trip from KLIA.

On May 8, 2007, I am expected to report to my new job. I am by the way hired by Shell Malaysia Bhd. SDN. Picture below is taken during my 1st day in Shell. According to them they always do this if they have new Joiners. In this time the new joiners are me and other 2 Pinoy guys. I am by the way a member now of Shell Information Technology Bhd SDN. GLUX team(Global Linux/Unix). This team is Level 2/3 support for thousands of server deployed globally.

2006-06-04T08:18:00.000+08:00

LVM on 3 SATA drives:

Scenario:

6x200G Sata Drive

3 raid 1 (hardware)

Challenge:

To create LVM on all 3 raid 1 drives excluding the partition used by OS.

Steps OS level:

1. Create Raid 1 on 6 drives = 3 Logical 200 GB

2. On OS install part. Create partition for OS (/, /home, /usr, swap)

3. On the remaining disk free space, create an LVM partition

4. Install OS.

Steps on LVM creation

1. Run pvcreate on the disk.

# pvcreate /dev/sda

# pvcreate /dev/sdb

# pvcreate /dev/sdc

2. Create a Volume Group

# vgcreate my_volume_group /dev/sda /dev/sdb /dev/sdc/

3. Run vgdisplay to verify the volume group

# vgdisplay

--- Volume Group ---

VG Name my_volume_group

VG Access read/write

VG Status available/resizable

VG # 1

MAX LV 256

Cur LV 0

Open LV 0

MAX LV Size 255.99 GB

Max PV 256

Cur PV 3

Act PV 3

VG Size 1.45 GB

PE Size 4 MB

Total PE 372

Alloc PE / Size 0 / 0

Free PE / Size 372/ 1.45 GB

VG UUID nP2PY5-5TOS-hLx0-FDu0-2a6N-f37x-0BME0Y

4. If the volume group looks correct, it is time to create a logical volume on top of the volume group

# lvcreate -L1G -nmy_logical_volume my_volume_group

5. Create a file system.

mkfs -t ext3 /dev/my_volume_group/my_logical_volume

6.Mount the filesystem.

FIN

2006-06-04T08:14:00.000+08:00

Apache config for SYMBIAN OS

AddType application/x-httpd-wml .wml

AddType application/x-httpd-php .wml

AddType text/vnd.wap.wml .wml

AddType image/vnd.wap.wbmp .wbmp

AddType application/vnd.wap.wmlc wmlc

AddType application/vnd.wap.wmlscriptc wmlsc

AddType application/x-httpd-php .php .phtml .wml .xhtml

AddType application/vnd.symbian.install .sis

mysql Forgoten Password

2005-06-09T10:24:00.000+08:00

This Sheet describes the procedure how to change the root password of MySQL server.

Stop MySQL server if its running.
# service mysqld stop
Check that MySQL daemon has stopped
# ps -jef | grep mysqld
Start MySQL as root
# su -
# /usr/libexec/mysqld -Sg --user=root &
Go back into MySQL with the client:
# mysql
mysql> use mysql
Now change the MySQL root password
mysql> UPDATE user SET password=password("newpassword") WHERE user="root";

mysql> flush privileges;

mysql> exit;
Stop MySQL server.
# killall mysqld
Verify that MySQL daemon is not running
# ps -jef | grep mysqld
Start MySQL the normal way, and all is good. For Red Hat this is:
# service mysqld start
Verify if MySQL daemon is running
# ps -jef | grep mysqld

That's it.

2005-06-06T17:46:00.000+08:00

running a script on background --- $nohup ./script-name.sh > nohup.ouputfile.txt& ---