Dosh

AIX LPAR: Replace failed mirror

2011-11-02T16:35:00.002+08:00

## break the mirror (two ways to do this)
rmlvcopy 1
unmirrorvg

## remove the disk from the vg
reducevg
## remove the hdisk from ODM
rmdev -dl

## physically replace the disk
diag -> function select -> task selection -> hot plug task -> scsi and scsi raid hot plug manager -> replace/remove a device attached to an scsi hot swap enclosure device -> select disk and follow instructions

## configure new disk an check the new number (hopefully the same)
cfgmgr -v
lsdev -Cc
## add back to volume group
extendvg
## create mirror (two ways to do this)
mklvcopy 2
mirrorvg

## sync mirror
syncvg -l

## If this is the rootvg there are additonal steps to take
bosboot -ad /dev/
bootlist -m normal
bootlist -m normal -o

AIX LPAR: Command

2011-11-02T16:20:00.000+08:00

bootinfo -b --> to see main boot disk
botlist -m normal hdisk0 hdisk1 net --> to change boot sequence
lsdev -Cc disk --> list device that is used
mount --> to check for mountpoint
errpt -a --> to check error details
lssrc -a --> to list daemon
lssrc -g telnet --> to list telnet daemon
stopsrc -t telnet --> stop telnet daemon

AIX LPAR: Increase or Decrease a file system JFS2

2011-11-02T14:31:00.000+08:00

{root_lpar5} / # lspv doshvg
0516-306 : Unable to find doshvg in the Device
        Configuration Database.
{root_lpar5} / # lsvg doshvg
VOLUME GROUP:       doshvg                   VG IDENTIFIER: 00fdc1c900004c0000000133646778de
VG STATE:           active                   PP SIZE:        4 megabyte(s)
VG PERMISSION:      read/write               TOTAL PPs:      1533 (6132 megabytes)
MAX LVs:            256                      FREE PPs:       1276 (5104 megabytes)
LVs:                2                        USED PPs:       257 (1028 megabytes)
OPEN LVs:           2                        QUORUM:         2 (Enabled)
TOTAL PVs:          3                        VG DESCRIPTORS: 3
STALE PVs:          0                        STALE PPs:      0
ACTIVE PVs:         3                        AUTO ON:        yes
MAX PPs per VG:     32512
MAX PPs per PV:     1016                     MAX PVs:        32
LTG size (Dynamic): 256 kilobyte(s)          AUTO SYNC:      no
HOT SPARE:          no                       BB POLICY:      relocatable
{root_lpar5} / # df -m /devilla
Filesystem    MB blocks      Free %Used    Iused %Iused Mounted on
/dev/fslv00     1024.00   1023.52    1%        5     1% /devilla
{root_lpar5} / # chfs -a size=+1024M /devilla
Filesystem size changed to 4194304
{root_lpar5} / # df -m /devilla
Filesystem    MB blocks      Free %Used    Iused %Iused Mounted on
/dev/fslv00     2048.00   2047.37    1%        5     1% /devilla
{root_lpar5} / # chfs -a size=-1024M /devilla
Filesystem size changed to 2097152
{root_lpar5} / # df -m /devilla
Filesystem    MB blocks      Free %Used    Iused %Iused Mounted on
/dev/fslv00     1024.00   1023.52    1%        5     1% /devilla

AIX LPAR: Create and Mount disk

2011-11-02T14:20:00.001+08:00

{root_lpar5} / # lspv
hdisk0          00fdc1c94bc59dc2                    rootvg          active
hdisk1          00fdc1c958b70cc0                    rootvg          active
hdisk2          00fdc1c95f7acf4a                    None
hdisk3          00fdc1c95f7acf93                    None
hdisk4          00fdc1c95f7acfdb                    None
hdisk5          00fdc1c963e5420f                    None
hdisk6          00fdc1c963e54259                    None
hdisk7          00fdc1c95f8023c4                    None
{root_lpar5} / # mkvg -y doshvg hdisk2 hdisk3 hdisk4
doshvg
{root_lpar5} / # lspv
hdisk0          00fdc1c94bc59dc2                    rootvg          active
hdisk1          00fdc1c958b70cc0                    rootvg          active
hdisk2          00fdc1c95f7acf4a                    doshvg          active
hdisk3          00fdc1c95f7acf93                    doshvg          active
hdisk4          00fdc1c95f7acfdb                    doshvg          active
hdisk5          00fdc1c963e5420f                    None
hdisk6          00fdc1c963e54259                    None
hdisk7          00fdc1c95f8023c4                    None
{root_lpar5} / # crfs -v jfs2 -m /devilla -g doshvg -a size=1024M -A yes
File system created successfully.
1048340 kilobytes total disk space.
New File System size is 2097152
{root_lpar5} / # mount /devilla
{root_lpar5} / # cd /devilla
{root_lpar5} /devilla # touch abc
{root_lpar5} /devilla # ls -al
total 8
drwxr-xr-x    3 root     system          256 Nov 02 14:12 .
drwxr-xr-x   22 root     system         4096 Nov 02 14:12 ..
-rw-r--r--    1 root     system            0 Nov 02 14:12 abc
drwxr-xr-x    2 root     system          256 Nov 02 14:12 lost+found
{root_lpar5} /devilla # df -m
Filesystem    MB blocks      Free %Used    Iused %Iused Mounted on
/dev/hd4         752.00    578.51   24%    12923     9% /
/dev/hd2        1864.00     32.02   99%    40353    79% /usr
/dev/hd9var      176.00    103.50   42%     4722    17% /var
/dev/hd3         168.00    166.23    2%       50     1% /tmp
/dev/hd1          16.00     15.60    3%       22     1% /home
/dev/hd11admin    128.00    127.64    1%        5     1% /admin
/proc                 -         -    -         -     - /proc
/dev/hd10opt     200.00     56.25   72%     2688    17% /opt
/dev/livedump    256.00    255.64    1%        4     1% /var/adm/ras/livedump
/dev/fslv00     1024.00   1023.52    1%        5     1% /devilla
{root_lpar5} / # lsfs /devilla
Name            Nodename   Mount Pt               VFS   Size    Options    Auto Accounting
/dev/fslv00     --         /devilla               jfs2 2097152 --         yes no
{root_lpar5} / # lsvg -l doshvg
doshvg:
LV NAME             TYPE       LPs     PPs     PVs LV STATE      MOUNT POINT
loglv00             jfs2log    1       1       1    open/syncd    N/A
fslv00              jfs2       256     256     1    open/syncd    /devilla

AIX LPAR: Mirror and Unmirror rootvg

2011-11-02T13:46:00.004+08:00

1. Extend Volume Group

{root_lpar5} / # lspv
hdisk0          00fdc1c94bc59dc2                    rootvg          active
hdisk1          00fdc1c958b70cc0                    None
hdisk2          00fdc1c95f7acf4a                    None
hdisk3          00fdc1c95f7acf93                    None
hdisk4          00fdc1c95f7acfdb                    None
hdisk5          00fdc1c963e5420f                    None
hdisk6          00fdc1c963e54259                    None
hdisk7          00fdc1c95f8023c4                    None
{root_lpar5} / # extendvg rootvg hdisk1
{root_lpar5} / # lspv
hdisk0          00fdc1c94bc59dc2                    rootvg          active
hdisk1          00fdc1c958b70cc0                    rootvg          active
hdisk2          00fdc1c95f7acf4a                    None
hdisk3          00fdc1c95f7acf93                    None
hdisk4          00fdc1c95f7acfdb                    None
hdisk5          00fdc1c963e5420f                    None
hdisk6          00fdc1c963e54259                    None
hdisk7          00fdc1c95f8023c4                    None

2. mirror with hdisk1

{root_lpar5} / # mirrorvg rootvg hdisk1
0516-1804 chvg: The quorum change takes effect immediately.

0516-1126 mirrorvg: rootvg successfully mirrored, user should perform
        bosboot of system to initialize boot records. Then, user must modify
        bootlist to include: hdisk0 hdisk1.
{root_lpar5} / #

3. Setting boot block to hdisk1

{root_lpar5} / # bosboot -ad /dev/hdisk1
bosboot: Boot image is 39638 512 byte blocks.

4. Setting boot list
{root_lpar5} / # bootlist -m normal hdisk0 hdisk1

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

To Unmirror rootvg

1. Remove mirror
{root_lpar5} / # unmirrorvg rootvg
0516-1246 rmlvcopy: If hd5 is the boot logical volume, please run 'chpv -c '
        as root user to clear the boot record and avoid a potential boot
        off an old boot image that may reside on the disk from which this
        logical volume is moved/removed.
0516-1804 chvg: The quorum change takes effect immediately.
0516-1144 unmirrorvg: rootvg successfully unmirrored, user should perform
        bosboot of system to reinitialize boot records. Then, user must modify
        bootlist to just include: hdisk0.

2. clear boot record
{root_lpar5} / # chpv -c hdisk1

3. Remove from volume group
{root_lpar5} / # reducevg rootvg hdisk1
{root_lpar5} / # lspv
hdisk0          00fdc1c94bc59dc2                    rootvg          active
hdisk1          00fdc1c958b70cc0                    None
hdisk2          00fdc1c95f7acf4a                    doshvg          active
hdisk3          00fdc1c95f7acf93                    doshvg          active
hdisk4          00fdc1c95f7acfdb                    doshvg          active
hdisk5          00fdc1c963e5420f                    None
hdisk6          00fdc1c963e54259                    None
hdisk7          00fdc1c95f8023c4                    None

to clear drive without rebooting

2011-10-05T11:03:00.002+08:00

to clear drive without rebooting
---------------------------------

p/s make sure the disk that need clear is not in use anymore.

format

5. c6t0d1
/pci@8,700000/lpfc@3/sd@0,1
6. c6t0d2
/pci@8,700000/lpfc@3/sd@0,2
7. c6t0d3
/pci@8,700000/lpfc@3/sd@0,3
8. c6t0d4

-root ~: powermt check
Warning: Symmetrix device path c6t0d1s0 is currently dead.
Do you want to remove it (y/n/a/q)? y
Warning: Symmetrix device path c6t0d2s0 is currently dead.
Do you want to remove it (y/n/a/q)? y
Warning: Symmetrix device path c6t0d3s0 is currently dead.
Do you want to remove it (y/n/a/q)? y
Warning: Symmetrix device path c6t0d4s0 is currently dead.
Do you want to remove it (y/n/a/q)? y

unconfigure disk if the disk is stuck at Veritas Volume manager

2011-06-10T00:18:00.000+08:00

1) Run the following command to rename 'es_rcm.pl' script.
# mv /etc/rcm/scripts/es_rcm.pl /etc/rcm/scripts/DONTUSE
NOTE: VxVM 4.1 and above 'es_rcm.pl' script is under /usr/lib/rcm/scripts
# mv /usr/lib/rcm/scripts/es_rcm.pl /usr/lib/rcm/scripts/DONTUSE
2) Run "/usr/sbin/cfgadm -c unconfigure ......" again. This command will finish successfully.
Example:

# /usr/sbin/cfgadm -c unconfigure c0::dsk/c0t0d0
3) After that, rename back file "DONTUSE" to the original name.
# mv /etc/rcm/scripts/DONTUSE /etc/rcm/scripts/es_rcm.pl
NOTE: VxVM 4.1 and above 'es_rcm.pl' script is under /usr/lib/rcm/scripts
# mv /usr/lib/rcm/scripts/DONTUSE /usr/lib/rcm/scripts/es_rcm.pl
4) Then physically replace the failed boot disk with new one.
5) Run the following command.
# cfgadm -c configure c0::dsk/c0t0d0
6) Run VERITAS Volume Manager[TM]'s usual procedure.
# /usr/sbin/vxdctl enable

printer on linux

2011-04-20T17:14:00.002+08:00

to check status
---------------

[root@server ~]# lpstat -oprintername

to enable printer
---------------------
[root@server ~]# /usr/bin/enable printername

to test print
-----------------
[root@server ~]# echo "test print from printername" | lp -dprintername ; lpstat -oprintername
request id is printername-695 (1 file)
printername1-695 root 1024 Wed 20 Apr 2011 09:30:28 AM BST

To remove jobs
---------------
[root@server ~]# lprm -Pprintername

simple one liner

2011-04-19T11:26:00.000+08:00

x=/etc/hosts

for i in $x; do ssh -q $i "uname -a; uptime; date" >> reports.log ; done

recovering boot archive solaris 10 on fail safe mode

2011-04-13T23:49:00.001+08:00

server at maintenance mode

# reboot -- -F failsafe

after server reboot and in failsafe mode
--------------------------------------

# df -h
Filesystem size used avail capacity Mounted on
/ramdisk-root:a 197M 175M 2.3M 99% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 31G 320K 31G 1% /etc/svc/volatile
objfs 0K 0K 0K 0% /system/object
sharefs 0K 0K 0K 0% /etc/dfs/sharetab
swap 31G 744K 31G 1% /tmp
/tmp/dev 31G 744K 31G 1% /dev
fd 0K 0K 0K 0% /dev/fd
# mount -o ro /dev/dsk/c3t0d0s0 /a
# cp /a/kernel/drv/md.conf /kernel/drv/md.conf
# umount /a
# update_drv -f md
devfsadm: mkdir failed for /dev 0x1ed: Read-only file system
# metainit -r
# metastat -c
d1 m 32GB d10 (maint) d11 (maint)
   d10 s 32GB c1t0d0s0
   d11 s 32GB c1t1d0s0
d2 m 16GB d20 (maint) d21 (maint)
   d20 s 16GB c1t0d0s5
   d21 s 16GB c1t1d0s5
d5 m 60GB d50 (maint) d51 (maint)
   d50 s 60GB c1t0d0s7
   d51 s 60GB c1t1d0s7
d4 m 4.0GB d40 (maint) d41 (maint)
   d40 s 4.0GB c1t0d0s6
   d41 s 4.0GB c1t1d0s6
d3 m 8.0GB d30 (maint) d31 (maint)
   d30 s 8.0GB c1t0d0s1
   d31 s 8.0GB c1t1d0s1
d6 m 16GB d60 (maint) d61 (maint)
   d60 s 16GB c1t0d0s4
   d61 s 16GB c1t1d0s4
# metasync -r
# metastat -c
d1 m 32GB d10 d11
   d10 s 32GB c1t0d0s0
   d11 s 32GB c1t1d0s0
d2 m 16GB d20 d21
   d20 s 16GB c1t0d0s5
   d21 s 16GB c1t1d0s5
d5 m 60GB d50 d51
   d50 s 60GB c1t0d0s7
   d51 s 60GB c1t1d0s7
d4 m 4.0GB d40 d41
   d40 s 4.0GB c1t0d0s6
   d41 s 4.0GB c1t1d0s6
d3 m 8.0GB d30 d31
   d30 s 8.0GB c1t0d0s1
   d31 s 8.0GB c1t1d0s1
d6 m 16GB d60 d61
   d60 s 16GB c1t0d0s4
   d61 s 16GB c1t1d0s4

# mount /dev/md/dsk/d1 /a
# bootadm update-archive -R /a
Creating boot_archive for /a
updating /a/platform/sun4u/boot_archive
# umount /a
# init 6
#
The system is being restarted.
syncing file systems... done
rebooting...

network tuning script

2011-04-12T18:51:00.001+08:00

#!/sbin/sh
# /etc/rc2.d/S68net-tune /etc/init.d/net-tune
# Copyright (c) 2000 by Sun Microsystems, Inc.
# All rights reserved.
#
#ident  "@(#)net-tune      1.6.4     030416 SMI ES-PTS-NET/Lor"
#
# Edit the following example code to suit your needs.
# Depending on your changes, this script overwrites the Sun recommended default
# values (To use the default values, you do not need this script). See Product
# Documentation and SunSolve Infodocs for proper use first (e.g. Infodocs 17416,
# 23041, 41665). Most parameters must be set on both sides to have effect
# (e.g. check switch and IP partner settings).
# To install:
# 1) cp S68net-tune to /etc/rc2.d
# 2) perform edits on the sript as required
# 3) chmod 744 /etc/rc2.d/S68net-tune
# 4) chown root:sys /etc/rc2.d/S68net-tune
# 5) ln /etc/rc2.d/S68net-tune /etc/init.d/net-tune

PATH=/usr/bin:/usr/sbin

case "$1" in
     'start')
 echo "Implementing Solaris Network Tuning."

# hme-Interfaces
# hme0
 #ndd -set /dev/hme instance 0
 #ndd -set /dev/hme adv_100T4_cap 0
 #ndd -set /dev/hme adv_100fdx_cap 1
 #ndd -set /dev/hme adv_100hdx_cap 0
 #ndd -set /dev/hme adv_10fdx_cap 0
 #ndd -set /dev/hme adv_10hdx_cap 0
 #ndd -set /dev/hme adv_autoneg_cap 0
# hme1
 #ndd -set /dev/hme instance 1
 #ndd -set /dev/hme adv_100T4_cap 0
 #ndd -set /dev/hme adv_100fdx_cap 1
 #ndd -set /dev/hme adv_100hdx_cap 0
 #ndd -set /dev/hme adv_10fdx_cap 0
 #ndd -set /dev/hme adv_10hdx_cap 0
 #ndd -set /dev/hme adv_autoneg_cap 0

# eri-Interfaces
# eri0
        #ndd -set /dev/eri instance 0
        #ndd -set /dev/eri adv_100T4_cap 0
        #ndd -set /dev/eri adv_100fdx_cap 1
        #ndd -set /dev/eri adv_100hdx_cap 0
        #ndd -set /dev/eri adv_10fdx_cap 0
        #ndd -set /dev/eri adv_10hdx_cap 0
        #ndd -set /dev/eri adv_autoneg_cap 0

# qfe-Interfaces
# qfe0
 #ndd -set /dev/qfe instance 0
 #ndd -set /dev/qfe adv_100T4_cap 0
 #ndd -set /dev/qfe adv_100fdx_cap 1
 #ndd -set /dev/qfe adv_100hdx_cap 0
 #ndd -set /dev/qfe adv_10fdx_cap 0
 #ndd -set /dev/qfe adv_10hdx_cap 0
 #ndd -set /dev/qfe adv_autoneg_cap 0
# qfe1
 #ndd -set /dev/qfe instance 1
 #ndd -set /dev/qfe adv_100T4_cap 0
 #ndd -set /dev/qfe adv_100fdx_cap 1
 #ndd -set /dev/qfe adv_100hdx_cap 0
 #ndd -set /dev/qfe adv_10fdx_cap 0
 #ndd -set /dev/qfe adv_10hdx_cap 0
 #ndd -set /dev/qfe adv_autoneg_cap 0

# dmfe-Interfaces (Netra X1)
# dmfe0
 #ndd -set /dev/dmfe0 adv_100fdx_cap 1
 #ndd -set /dev/dmfe0 adv_100hdx_cap 0
 #ndd -set /dev/dmfe0 adv_10fdx_cap 0
 #ndd -set /dev/dmfe0 adv_10hdx_cap 0
 #ndd -set /dev/dmfe0 adv_autoneg_cap 0
# dmfe1
 #ndd -set /dev/dmfe1 adv_100fdx_cap 1
 #ndd -set /dev/dmfe1 adv_100hdx_cap 0
 #ndd -set /dev/dmfe1 adv_10fdx_cap 0
 #ndd -set /dev/dmfe1 adv_10hdx_cap 0
 #ndd -set /dev/dmfe1 adv_autoneg_cap 0

# vge-Interfaces (Gigabit 1.x)
# vge0
 #ndd -set /dev/vge instance 0
 #ndd -set /dev/vge fdr_filter 1
 #ndd -set /dev/vge link_negotiation 0
# vge1
 #ndd -set /dev/vge instance 1
 #ndd -set /dev/vge fdr_filter 1
 #ndd -set /dev/vge link_negotiation 0

# ge-Interfaces (Gigabit 2.x and 3.x)
# example: forced 1000 Mbit/s, 802.3x Flow Control send and receive
# check if your NIC is 802.3x capable (ndd parameter pause_cap, asm_dir_cap) 
# ge0
 #ndd -set /dev/ge instance 0
 #ndd -set /dev/ge adv_1000fdx_cap 1
 #ndd -set /dev/ge adv_1000hdx_cap 0
        #ndd -set /dev/ge adv_pauseTX 1
 #ndd -set /dev/ge adv_pauseRX 1
 #ndd -set /dev/ge adv_1000autoneg_cap 0
# ge1
 #ndd -set /dev/ge instance 1
 #ndd -set /dev/ge adv_1000fdx_cap 1
 #ndd -set /dev/ge adv_1000hdx_cap 0
        #ndd -set /dev/ge adv_pauseTX 1
 #ndd -set /dev/ge adv_pauseRX 1
 #ndd -set /dev/ge adv_1000autoneg_cap 0

# ce-Interfaces (GigaSwift 1.0 UTP)
# example: forced 1000 Mbit/s, 802.3x Flow Control send and receive
# ce0
 #ndd -set /dev/ce instance 0
        # Master values, change in forced 1000 Mbit/s back-to-back config only:
        #ndd -set /dev/ce link_master 0 # one link partner 1, the other 0 (ce <=1.118)
        #ndd -set /dev/ce master_cfg_enable 1 # enable usage of master_cfg_value (ce >1.118)
        #ndd -set /dev/ce master_cfg_value 0  # one link partner 1, the other 0 (ce >1.118)
        # Speed/Mode values, set the desired to 1, all other to 0:
 #ndd -set /dev/ce adv_1000fdx_cap 1
 #ndd -set /dev/ce adv_1000hdx_cap 0
 #ndd -set /dev/ce adv_100fdx_cap 0
 #ndd -set /dev/ce adv_100hdx_cap 0
 #ndd -set /dev/ce adv_10fdx_cap 0
 #ndd -set /dev/ce adv_10hdx_cap 0
        #ndd -set /dev/ce adv_asmpause_cap 0
        #ndd -set /dev/ce adv_pause_cap 1
 #ndd -set /dev/ce adv_autoneg_cap 0
# ce1
 #ndd -set /dev/ce instance 1
        # Master values, change in forced 1000 Mbit/s back-to-back config only:
        #ndd -set /dev/ce link_master 0 # one link partner 1, the other 0 (ce <=1.118)
        #ndd -set /dev/ce master_cfg_enable 1 # enable usage of master_cfg_value (ce >1.118)
        #ndd -set /dev/ce master_cfg_value 0  # one link partner 1, the other 0 (ce >1.118)
        # Speed/Mode values, set the desired to 1, all other to 0:
 #ndd -set /dev/ce adv_1000fdx_cap 1
 #ndd -set /dev/ce adv_1000hdx_cap 0
 #ndd -set /dev/ce adv_100fdx_cap 0
 #ndd -set /dev/ce adv_100hdx_cap 0
 #ndd -set /dev/ce adv_10fdx_cap 0
 #ndd -set /dev/ce adv_10hdx_cap 0
        #ndd -set /dev/ce adv_asmpause_cap 0
        #ndd -set /dev/ce adv_pause_cap 1
 #ndd -set /dev/ce adv_autoneg_cap 0

# switch MTU path discovery off
 #ndd -set /dev/ip ip_path_mtu_discovery 0
# TCP/UDP buffer tunings
 #ndd -set /dev/tcp tcp_xmit_hiwat 65536
 #ndd -set /dev/tcp tcp_recv_hiwat 65536
 #ndd -set /dev/udp udp_xmit_hiwat 65536
 #ndd -set /dev/udp udp_recv_hiwat 65536
# TCP congestion window size, for Solaris <= 2.5, only
 #ndd -set /dev/tcp tcp_cwnd_max 65535
# Change TCP maximum retransmission interval, for Solaris <= 7, only
        #ndd -set /dev/tcp tcp_rexmit_interval_max 60000
# Change number of TCP slow start initial packets to work arround
# slow start bug in BSD stack and Windows. For Solaris <= 7, only
        #ndd -set /dev/tcp tcp_slow_start_initial 2 

         ;;

     'stop')
         echo "No kernel parameters changed."
         ;;

        *)
         echo "Usage: $0 {start|stop}"
         ;;

  esac
  exit 0

To srhink /local by 1GB on linux RHEL v5 with LVM/resize2fs.

2011-03-27T11:02:00.002+08:00

Goal: To srhink /local by 1GB on linux RHEL v5 with LVM/resize2fs.

1* Requirement:- Need to un-mount fs before we can shrink

[root@server ~]# df -h /local
Filesystem            Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol06
                      104G 188M 104G   1% /local

[root@server ~]# umount /local/
[root@server ~]# e2fsck -f /dev/VolGroup00/LogVol06
e2fsck 1.39 (29-May-2006)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/local: 11/13844480 files (9.1% non-contiguous), 482513/27672576 blocks
[root@server ~]# lvdisplay /dev/VolGroup00/LogVol06
--- Logical volume ---
LV Name                /dev/VolGroup00/LogVol06
VG Name                VolGroup00
LV UUID                8R6U7b-tKOY-Wqbt-2BKn-u3nN-Yxl9-0LTvZE
LV Write Access        read/write
LV Status              available
# open                 1
LV Size                105.56 GB
Current LE             3378
Segments               1
Allocation             inherit
Read ahead sectors     auto
- currently set to     256
Block device           253:5

[root@server ~]# resize2fs /dev/VolGroup00/LogVol06 104G  Reduce to 104G because lvdisplay shows LV Size is actually 105.56GB even though df -h shows 104 is the total size.
resize2fs 1.39 (29-May-2006)
Resizing the filesystem on /dev/VolGroup00/LogVol06 to 27262976 (4k) blocks.
The filesystem on /dev/VolGroup00/LogVol06 is now 27262976 blocks long.

[root@server ~]# mount /local
[root@server ~]# df -h /local
Filesystem            Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol06
                      103G 188M 103G   1% /local

[root@server ~]# lvreduce -L -1G /dev/VolGroup00/LogVol06
WARNING: Reducing active and open logical volume to 104.56 GB
THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce LogVol06? [y/n]: y
Reducing logical volume LogVol06 to 104.56 GB
Logical volume LogVol06 successfully resized
[root@server ~]# df -h /local
Filesystem            Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol06
                      103G 188M 103G   1% /local
[root@server ~]# lvdisplay /dev/VolGroup00/LogVol06
--- Logical volume ---
LV Name                /dev/VolGroup00/LogVol06
VG Name                VolGroup00
LV UUID                8R6U7b-tKOY-Wqbt-2BKn-u3nN-Yxl9-0LTvZE
LV Write Access        read/write
LV Status              available
# open                 1
LV Size                104.56 GB
Current LE             3346
Segments               1
Allocation             inherit
Read ahead sectors     auto
- currently set to     256
Block device           253:5

[root@server ~]# umount /local
[root@server ~]# e2fsck -f /dev/VolGroup00/LogVol06  Verify again filesystem is okay after resize & lvreduce
e2fsck 1.39 (29-May-2006)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/local: 11/13631488 files (9.1% non-contiguous), 475831/27262976 blocks

[root@server ~]# df -h /local
Filesystem            Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol06
                      103G 188M 103G   1% /local

End result is that size is reduced by 1GB and not 2GB like if we used 103G at the resize2fs parameter.

[root@server ~]# vgdisplay
--- Volume group ---
VG Name               VolGroup00
System ID
Format                lvm2
Metadata Areas        1
Metadata Sequence No 13
VG Access             read/write
VG Status             resizable
MAX LV                0
Cur LV                7
Open LV               7
Max PV                0
Cur PV                1
Act PV                1
VG Size               136.56 GB
PE Size               32.00 MB
Total PE              4370
Alloc PE / Size       4338 / 135.56 GB
Free PE / Size       32 / 1.00 GB  Verify that 1GB free space left after lvreduce / resize2fs
VG UUID               18QiUj-1s0O-6qGt-GujM-cPOi-acw1-HVgOUX

install bootblk

2011-02-17T21:30:00.002+08:00

/usr/bin/installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/cXtXdXsX

Step to enable sendmail if port 25 is disable

2011-01-24T21:59:00.002+08:00

Step to enable sendmail if port 25 is disable

# svccfg -s sendmail listprop
more

config application

config/value_authorization astring solaris.smf.value.sendmail

config/include_info boolean false

config/local_only boolean true <<<< ----------------------------

config/path_to_sendmail_mc astring

config-file dependency

config-file/entities fmri file://localhost/etc/mail/sendmail.cf

config-file/grouping astring require_all

config-file/restart_on astring refresh

config-file/type astring path

nsswitch dependency

nsswitch/entities fmri file://localhost/etc/nsswitch.conf

nsswitch/grouping astring require_all

nsswitch/restart_on astring refresh

nsswitch/type astring path

autofs dependency

autofs/entities fmri svc:/system/filesystem/autofs

autofs/grouping astring optional_all

autofs/restart_on astring none

autofs/type astring service

dependents framework

dependents/smtp-sendmail_multi-user fmri svc:/milestone/multi-user

startd framework

startd/ignore_error astring core,signal

general framework

general/action_authorization astring solaris.smf.manage.sendmail

general/enabled boolean true

start method

start/exec astring "/lib/svc/method/smtp-sendmail start"

start/timeout_seconds count 120

start/type astring method

stop method

stop/exec astring "/lib/svc/method/smtp-sendmail stop %{restarter/contract}"

#svccfg -s sendmail setprop config/local_only=false

# svcadm refresh sendmail

# svcadm restart sendmail

# telnet localhost 25

Trying 127.0.0.1...

Connected to localhost.

Escape character is '^]'.

220 server.um.us.sbphrd.com ESMTP Sendmail 8.14.4+Sun/8.13.7; Mon, 24 Jan 2011 08:18:39 -0500 (EST)

^C^]

telnet> quit

Connection to localhost closed.

testing

# echo "Subject: test"
/usr/lib/sendmail -v

SSH Without a Password

2011-01-16T20:45:00.000+08:00

The following steps can be used to ssh from one system to another without specifying a password.

Notes:

The system from which the ssh session is started via the ssh command is the client.

The system that the ssh session connects to is the server.

These steps seem to work on systems running OpenSSH.

The steps assume that a DSA key is being used. To use a RSA key substitute 'rsa' for 'dsa'.

The steps assume that you are using a Bourne-like shell (sh, ksh or bash)

Some of this information came from:

http://www.der-keiler.de/Mailing-Lists/securityfocus/Secure_Shell/2002-12/0083.html

Steps:

On the client run the following commands:

$ mkdir -p $HOME/.ssh

$ chmod 0700 $HOME/.ssh

$ ssh-keygen -t dsa -f $HOME/.ssh/id_dsa -P ''

This should result in two files, $HOME/.ssh/id_dsa (private key) and $HOME/.ssh/id_dsa.pub (public key).

Copy $HOME/.ssh/id_dsa.pub to the server.

On the server run the following commands:

$ cat id_dsa.pub >> $HOME/.ssh/authorized_keys2

$ chmod 0600 $HOME/.ssh/authorized_keys2

Depending on the version of OpenSSH the following commands may also be required:

$ cat id_dsa.pub >> $HOME/.ssh/authorized_keys

$ chmod 0600 $HOME/.ssh/authorized_keys

An alternative is to create a link from authorized_keys2 to authorized_keys:

$ cd $HOME/.ssh && ln -s authorized_keys2 authorized_keys

On the client test the results by ssh'ing to the server:

$ ssh -i $HOME/.ssh/id_dsa server

(Optional) Add the following $HOME/.ssh/config on the client:

Host server

IdentityFile ~/.ssh/id_dsa

This allows ssh access to the server without having to specify the path to the id_dsa file as an argument to ssh each time.

detect and mount disk in linux VM

2011-01-16T02:10:00.000+08:00

[root@server ~]# cat /proc/scsi/scsi

Attached devices:

Host: scsi0 Channel: 00 Id: 00 Lun: 00

Vendor: VMware Model: Virtual disk Rev: 1.0

Type: Direct-Access ANSI SCSI revision: 02

[root@server ~]# echo "scsi add-single-device 0 0 1 0" > /proc/scsi/scsi

[root@server ~]# tail -3 /var/log/messages

Jan 15 12:45:48 server kernel: sdb: unknown partition table

Jan 15 12:45:48 server kernel: sd 0:0:1:0: Attached scsi disk sdb

Jan 15 12:45:48 server kernel: sd 0:0:1:0: Attached scsi generic sg1 type 0

[root@server ~]# cd /dev/

[root@server dev]# fdisk -l

Disk /dev/sda: 38.6 GB, 38654705664 bytes

255 heads, 63 sectors/track, 4699 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sda1 * 1 17 131072+ 83 Linux

Partition 1 does not end on cylinder boundary.

/dev/sda2 17 4700 37617568 8e Linux LVM

Disk /dev/sdb: 59.0 GB, 59055800320 bytes

255 heads, 63 sectors/track, 7179 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdb doesn't contain a valid partition table

[root@server dev]# ./MAKEDEV sdb

[root@server dev]# fdisk -l

Disk /dev/sda: 38.6 GB, 38654705664 bytes

255 heads, 63 sectors/track, 4699 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sda1 * 1 17 131072+ 83 Linux

Partition 1 does not end on cylinder boundary.

/dev/sda2 17 4700 37617568 8e Linux LVM

Disk /dev/sdb: 59.0 GB, 59055800320 bytes

255 heads, 63 sectors/track, 7179 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdb doesn't contain a valid partition table

[root@server dev]# pvcreate /dev/sdb

Physical volume "/dev/sdb" successfully created

[root@server dev]# vgcreate VolGroup01 /dev/sdb

Volume group "VolGroup01" successfully created

[root@server dev]# vgdisplay

--- Volume group ---

VG Name VolGroup01

System ID

Format lvm2

Metadata Areas 1

Metadata Sequence No 1

VG Access read/write

VG Status resizable

MAX LV 0

Cur LV 0

Open LV 0

Max PV 0

Cur PV 1

Act PV 1

VG Size 55.00 GB

PE Size 4.00 MB

Total PE 14079

Alloc PE / Size 0 / 0

Free PE / Size 14079 / 55.00 GB

VG UUID 0CIkNO-1gus-k7o3-fFPd-6lCW-UdJD-y9jpro

--- Volume group ---

VG Name VolGroup00

System ID

Format lvm2

Metadata Areas 1

Metadata Sequence No 8

VG Access read/write

VG Status resizable

MAX LV 0

Cur LV 7

Open LV 7

Max PV 0

Cur PV 1

Act PV 1

VG Size 35.84 GB

PE Size 32.00 MB

Total PE 1147

Alloc PE / Size 1147 / 35.84 GB

Free PE / Size 0 / 0

VG UUID reWZnW-Pgco-u2sT-cI3v-yDUS-Ku3H-yDhuYk

[root@server dev]# vgdisplay VolGroup01
grep pe

Open LV 0

[root@server dev]# vgdisplay VolGroup01
grep PE

PE Size 4.00 MB

Total PE 14079

Alloc PE / Size 0 / 0

Free PE / Size 14079 / 55.00 GB

[root@server dev]# lvcreate -l 14079 -n LogVol00 VolGroup01

Logical volume "LogVol00" created

[root@server dev]# lvdisplay /dev/VolGroup01/LogVol00

--- Logical volume ---

LV Name /dev/VolGroup01/LogVol00

VG Name VolGroup01

LV UUID 2BWVtT-mBnf-LXNC-UBtk-r4em-RQ4u-YdcudY

LV Write Access read/write

LV Status available

# open 0

LV Size 55.00 GB

Current LE 14079

Segments 1

Allocation inherit

Read ahead sectors auto

- currently set to 256

Block device 253:7

[root@server dev]# mkfs.ext3 -m0 /dev/VolGroup01/LogVol00 -L /local

mke2fs 1.39 (29-May-2006)

Filesystem label=/local

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

7208960 inodes, 14416896 blocks

0 blocks (0.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=4294967296

440 block groups

32768 blocks per group, 32768 fragments per group

16384 inodes per group

Superblock backups stored on blocks:

32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,

4096000, 7962624, 11239424

Writing inode tables: done

Creating journal (32768 blocks): done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 35 mounts or

180 days, whichever comes first. Use tune2fs -c or -i to override.

[root@server dev]# vi /etc/fstab

[root@server dev]# vi /etc/fstab

[root@server dev]# mkdir /scratch

[root@server dev]# umount /local

[root@server dev]# df -h

Filesystem Size Used Avail Use% Mounted on

/dev/mapper/VolGroup00-LogVol00

992M 448M 493M 48% /

/dev/mapper/VolGroup00-LogVol05

2.0G 69M 1.8G 4% /tmp

/dev/mapper/VolGroup00-LogVol01

16G 2.6G 13G 18% /usr

/dev/mapper/VolGroup00-LogVol02

2.0G 503M 1.4G 27% /var

/dev/mapper/VolGroup00-LogVol03

992M 34M 908M 4% /opt/patrol

/dev/sda1 124M 19M 99M 16% /boot

tmpfs 187M 0 187M 0% /dev/shm

[root@server dev]# mount /local

[root@server dev]# mount /scratch

[root@server dev]# df -h

Filesystem Size Used Avail Use% Mounted on

/dev/mapper/VolGroup00-LogVol00

992M 448M 493M 48% /

/dev/mapper/VolGroup00-LogVol05

2.0G 69M 1.8G 4% /tmp

/dev/mapper/VolGroup00-LogVol01

16G 2.6G 13G 18% /usr

/dev/mapper/VolGroup00-LogVol02

2.0G 503M 1.4G 27% /var

/dev/mapper/VolGroup00-LogVol03

992M 34M 908M 4% /opt/patrol

/dev/sda1 124M 19M 99M 16% /boot

tmpfs 187M 0 187M 0% /dev/shm

/dev/mapper/VolGroup01-LogVol00

55G 180M 54G 1% /local

/dev/mapper/VolGroup00-LogVol06

5.7G 140M 5.3G 3% /scratch

[root@server dev]# e2label /dev/

Display all 618 possibilities? (y or n)

[root@server dev]# e2label /dev/VolGroup01/LogVol00

/local

[root@server dev]# cat /etc/fstab

/dev/VolGroup00/LogVol00 / ext3 defaults 1 1

/dev/VolGroup00/LogVol05 /tmp ext3 defaults 1 2

/dev/VolGroup00/LogVol06 /scratch ext3 defaults 1 2

/dev/VolGroup00/LogVol01 /usr ext3 defaults 1 2

/dev/VolGroup00/LogVol02 /var ext3 defaults 1 2

/dev/VolGroup00/LogVol03 /opt/patrol ext3 defaults 1 2

LABEL=/boot /boot ext3 defaults 1 2

tmpfs /dev/shm tmpfs defaults 0 0

devpts /dev/pts devpts gid=5,mode=620 0 0

sysfs /sys sysfs defaults 0 0

proc /proc proc defaults 0 0

/dev/VolGroup00/LogVol04 swap swap defaults 0 0

LABEL=/local /local ext3 defaults 1 2

How to find file in Unix

2010-12-21T11:31:00.000+08:00

find file in var that have larger size
---------------------------------------

find /var -xdev -size +10000 -exec ls -l {} \; sort +4n

find file in tmp with name
----------------------------
find /tmp -name core

checking and fix array battery

2010-12-07T04:54:00.002+08:00

bash-2.03# /usr/lib/osa/bin/healthck c5t5d0

Health Check Summary Information

da042_003: Failed Battery

healthck succeeded!
bash-2.03# /usr/lib/osa/bin/raidutil -c c5t5d0 -B
LUNs found on c5t5d0.
LUN 0 RAID 3 94570 MB
Battery age is between 810 days and 900 days.

raidutil succeeded!
bash-2.03# /usr/lib/osa/bin/raidutil -c c5t5d0 -R
LUNs found on c5t5d0.
LUN 0 RAID 3 94570 MB

raidutil succeeded!
bash-2.03# /usr/lib/osa/bin/raidutil -c c5t5d0 -B
LUNs found on c5t5d0.
LUN 0 RAID 3 94570 MB
Battery age is between 0 days and 90 days.

raidutil succeeded!
bash-2.03# /usr/lib/osa/bin/healthck c5t5d0

Health Check Summary Information

da042_003: Optimal

healthck succeeded!

how to resetsc / resetrsc

2010-12-07T04:52:00.000+08:00

/usr/platform/SUNW,Sun-Fire-V440/sbin/scadm resetsc
/usr/platform/SUNW,Sun-Fire-V440/sbin/scadm resetrsc

CUPS Local Printer Configuration Linux

2010-11-30T04:51:00.002+08:00

The lpadmin command is used to configure printers. The following is an example of setting up a laser printer with CUPS. You will have to become root or use sudo to execute these commands:

====================================================================================
/usr/sbin/lpadmin -p Laser -v parallel:/dev/lp0 -P /root/laser.ppd
/usr/bin/enable Laser
/usr/sbin/accept Laser
/usr/sbin/lpadmin -d Laser
====================================================================================

Please note that bash has a builtin command called enable, so bash users must use the full path (/usr/bin/enable) to enable printers.

The first command creates a new printer called "Laser" that is connected to the first parallel port and is using the PPD file /root/laser.ppd. "Laser" is then enabled and told to accept jobs with the enable and accept commands. The last command sets "Laser" as the default printer.

If your printer is connected to a USB port or if you do not know the correct device-uri for your printer try running /usr/sbin/lpinfo -v to get a list of available printer devices.

Make sure your printer's page size and other options are set correctly by running /usr/bin/lpoptions -l. More detailed information about printer configuration is available in the CUPS documentation.

How do I configure a Netdump Server and a Netdump Client in Red Hat Enterprise Linux?

2010-09-16T11:39:00.000+08:00

Issue

How do I configure a Netdump Server and a Netdump Client in Red Hat Enterprise Linux?

Environment

Red Hat Enterprise Linux 3, Red Hat Enterprise Linux 4
Netdump

Resolution

Netdump is used for capturing vmcores and diagnose kernel panics.
Netdump requires there to be a Netdump server and then any number of clients.

Setup on netdump server and client

Server Configuration:

Verify that the netdump server is installed: rpm -q netdump-server. If it is not installed, install it by running the command: up2date netdump-server.
After the netdump server package is installed change the password for the "netdump" user to something that you know: passwd netdump
Enable the netdump server: chkconfig netdump-server on
Start the netdump server: service netdump-server start

Client Configuration:

Verify that the netdump client is installed: rpm -q netdump. If it is not installed, install it by running the command: up2date netdump.
Edit /etc/sysconfig/netdump and add the following line:
```
NETDUMPADDR=192.168.0.5 
```
**192.168.0.5 should be changed to the ip address of the netdump server.
Enter the following command and give the netdump password when prompted: service netdump propagate
Enable the netdump client: chkconfig netdump on
Start the netdump client: service netdump start

At this point all sysrq command entered should be sent accross the network to the netdump server where they should be stored in the /var/crash directory. Dump files generated by netdump should be named vmcore by default.

Test Method

To test if the netdump configuration is correct, perform the following on the netdump client (Warning: it will crash the machine!):

sysctl -w kernel.sysrq=1
echo c > /proc/sysrq-trigger

This will crash the system and you will see a kernel dump on the netdump server in the directory /var/crash//. You will see the file "vmcore-incomplete" while the client is dumping data to the server. The file is renamed to "vmcore" once it is completed.

The size of "vmcore" will vary and may reach several gigs. On a system with 512Mb of RAM, the above test created a vmcore of approximately 510Mb.

Troubleshooting

Netdump client service startup failures are usually due to NIC or module incompatibility problems. You will notice "insmod" errors when this happens.

Netdump does not work for all NICs so make sure that yours is compatible. Below is a list of supported NICs at the time of writing:

Broadcom bcm57xx using the tg3 driver. Does not work with bcm5700 driver.
3Com 3c59x
Intel eepro100, e100 and e1000
tlan
tulip

And netdump can not work with virtio-net driver either, so if you need to setup netdump on a KVM guest, you should choose a network model which can support netdump, rather than virtio-net driver.

/tmp is 100% but inode is only 1%??

2010-09-08T08:43:00.003+08:00

/tmp is 100% but inode is only 1%. this is due to some process are tied with the deleted file. issue lsof +aL1 /tmp and kill the process to freed the FS.

[server tmp]# df -h /tmp
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol05
2.0G 1.9G 0 100% /tmp
[server tmp]# df -i /tmp
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/mapper/VolGroup00-LogVol05
262144 23 262121 1% /tmp
[server tmp]# lsof +aL1 /tmp
COMMAND PID USER FD TYPE DEVICE SIZE NLINK NODE NAME
java 18871 platpra1 169w REG 253,3 1967697920 0 212996 /tmp/DataEngine_26214400/BirtDataTemp12839026526150/session_12839026526350/goalFile (deleted)
[server tmp]# kill -9 18871
[server tmp]# df -h /tmp
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol05
2.0G 36M 1.9G 2% /tmp

for proper cleanup, please fuser the directory before deleting any of it.

sendmail

2010-09-08T07:23:00.000+08:00

Sending e-mail using shell scripts

Most script programmers already know how easy it is to send e-mail from within shell scripts. A simple invocation of the mail program with the recipient for a command line argument will send all data read from standard input:

    $ mail root < /tmp/db_reorg.log

   $ echo "Coming home for dinner!" | mail sylvia@home.com

The "mail" command accepts additional command line parameters, e.g.

-s subject Use subject for the e-mail title

-c address Send copy of the mail to the specified address

-b address Send blind carbon copy to specified address

Some common usage examples:

    Send a log file to the system administrator:

   # mail -s "Reorganization completed" root < db_reorg.log



   Send mail to "mark" with copy to "john":

   $ echo "John's coming with us" |

       mail -c john -s "Join us watching Star Wars" mark

Portability

Note that not all mail commands have an "-s" option to specify a mail subject. Sometimes an extended version of the mail command is available with the name "mailx", e.g. /usr/ucb/mailx, or "Mail" (with a capital "M").

But how can we "attach" a file to a mail? We know that newer mail readers like Mozilla, Netscape Messenger or Microsoft Exchange have a way of displaying file attachments, e.g. images, ZIP files or audio files. How can we send some mail text (e.g. "See this picture of me surfing!") together with a binary file (e.g. "surfing.jpeg")?

The next chapter describes the traditional approach using "uuencode".

File attachments with "uuencode"

Sending binary files does not work well for the Internet. We could send a binary file "surfing.jpeg" using this command:

mail -s "picture of me surfing" sylvia@home.com <>

  but chances are high that the image will be unusable the time it arrives at the recipient.  During mail delivery the mail is relayed from one mail delivery agent to the next, until it finally arrives at the recipient. Each delivery agent may transform the mail message, e.g. by stripping the 8th bit of each character, removing NUL bytes (ASCII code 0), converting the end-of-line character LF ("line-feed", ASCII code 12) to a local representation (e.g. CR LF), or removing trailing space or TAB characters from each line.  
Since only some characters are sure to arrive unmodified, the traditional solution is to encode the mail from binary format to a text format that is safe to transmit. The program used for this is called "uuencode" ("UNIX to UNIX encoding"), the program to decode the data is called "uudecode".  
The simplest way to send a file as a mail attachment is shown by the following example:  
        $ uuencode surfing.jpeg surfing.jpeg | mail sylvia@home.com
   
 
  That's all! If Sylvia uses a current mail reader like Mozilla, Netscape Messenger or Microsoft Exchange, she will see a mail containing just one file attachment: the file "surfing.jpeg". In the command above we had to specify the file name two times: the first name denotes the input file to be encoded, and the second name is the file name the recipient will see.  
This way we can include normal text, too:  
        $ (cat mailtext; uuencode surfing.jpeg surfing.jpeg) |

       mail sylvia@home.com
   
    Note: The file name "surfing.jpeg" again appears twice on   the uuencode command line: the first time to   specify the input file name, the second time for the remote   extraction file name.  
  The first "cat" will prepend the contents of the file "mailtext" to the "uuencode"ed data of the image "surfing.jpeg". Both commands are executed within a sub shell, to combine the output of both commands to one output stream redirected to the "mail" command.  
This method of sending file attachments works fairly well, but still has some shortcomings:  
Many user agents cannot directly decode this kind of file     attachments, e.g. "Eudora". Some mail agents explicitly     require the decoding of the mail using the program     "uudecode"   
The "uuencode" encoding is not standardized. Text encoded on  one system     may not be decoded correctly by the recipient's system      [the content of the mail message was saved to

   the file "mail.uue"]

   $ uudecode mail.uue

   The file "surfing.jpeg" was written to the current directory
  
  The next method does not have this disadvantages. It works with most (newer) mail user agents and uses the "Multipurpose Internet Mail Extensions" (MIME).  
Top  of document   
   File attachments with MIME
  The MIME Standard ("Multipurpose Internet Mail Extensions") defines an impressive list of new features for e-mail messages, e.g.  arbitrary file attachments, e.g. images, audio files   
more than one file attachment per mail   
multi-part messages 
  Other features are non-ASCII character sets for message bodies and message headers.  
But how can shell programmers use these features effectively?  
At first there has to be a command-line driven program to send MIME mails.  There are some MIME packages available free of charge, the most common being  
mutt written by Michael Elkins     (http://www.mutt.org)    
MetaMail by Nathaniel S.Borenstein     (ftp://ftp.research.telcordia.com/pub/nsb/)    
mpack by John G. Myers     (ftp://ftp.andrew.cmu.edu:/pub/mpack/)  
  But check your local system before downloading one of these packages, many UNIX systems (e.g. Linux) come with one or more of them pre-installed.  
mutt is an interactive, text-oriented e-mail client. Not very useful for usage in a script, one might think. But on closer view the program turns out to provide an easy way to send e-mails with file attachments. Have a look at the following example:  
        $ mutt -s "Birthday celebration" -a citymap.jpg all@friends.org \

   	<>   
 
  This command shows how to specify four important parts of an e-mail:  The recipient ("all@friends.org")   
The main body of the e-mail (read from standard input,     here redirected from the file "invitation.txt")   
An attachment (with option -a)   
A subject line (option -s) 
  The interesting part is the option -a, which allows us to send an attachment (in this case a picture of a city map). We could have added more attachments by using multiple -a options.  mutt always reads a text from standard input that will become the main body of the e-mail, the text before the attachment. If the mail should consist of attachments only, we can either specify /dev/null as the file to read, e.g.  
        $ mutt -a syslogs.tar.gz admin@domain.org < /dev/null
   
 
  or use an empty line as the mail body:          $ echo | mutt -a syslogs.tar.gz admin@domain.org
   
 
  mutt does some work behind the scenes, e.g. it's looking at the file extensions of the attachments, and selects an appropriate MIME type for each. This works reasonably well (depending on the configuration of the system in general and mutt in particular), but if more control about MIME types and the sending of the e-mail is required, the next package may be more appropriate.  The remainder of this chapter will use programs of the MetaMail package for the examples. Don't worry if the command lines seem somewhat cryptic, at the end of this article we will present a script simplifying the sending of mail attachments.  
MetaMail provides two programs to send mail: mailto and metasend. We will use the second one for scripting, because it can be used non-interactively. The most interesting command line arguments of metasend are listed in the following table [refer to metasend(1) for a complete list].  
     -b      batch (non-interactive) mode

   
    -c cc      CC address (for copy of the mail)

   
    -f filename      Name of file to attach

   
    -m MIME-type       MIME content type, e.g. "text/plain" or     "application/octet-stream"

    
    -s subject      Title (subject) of the mail message

   
    -t to      Recipient's address

   
    -n      Next file attachment (needed for multiple file attachments)

   
    -D description      Description of the file content

   
    -o outputfile      Name of an output file. If the -t option     is given, the mail is sent directly to the addressee

   
  
 
  This new knowledge enables us to send an audio file using "metasend":  
        $ metasend -b -t john@friends.org -s "Hear our son!" \

   	-m audio/basic -f crying.au
   
 
  This invocation of "metasend" sends a mail to "john@friends.org" (option -t) with the subject "Hear our son!" (option -s), without prompting for further arguments (option -b). Without the "-b" argument, the command would have asked for addresses to send "carbon copies" to. The file to attach is called "crying.au", and the file type is "audio/basic".  
The file type (or "MIME-type") "audio/basic" gives the recipient's mail reader a hint on the contents of the file attachment. Some contents may be displayed directly (e.g. "text/plain", "image/gif"), for others the mail reader may call external programs to present the contents (e.g. "application/postscript", "audio/wav"). The relation between MIME content type and external program to call often is established using a file called "mailcap" (see mailcap(4), if available on your system). Mozilla or Netscape's Communicator allows to specify "helper applications" that are invoked depending on the MIME type.  
An annoying property of "metasend" is the need to specify the MIME type for each file. The script  sendfile  simplifies this. The following example sends two files, "cover.gif" and "contents.ps":  
        $ sendfile editor@somewhere.com cover.gif contents.ps

   [Text to appear before the attachments, EOF to end]

   Hello John, you'll find a table of contents attached to

   this e-mail.

   ^D
   
 
  The script is easier to use because it determines the MIME type of the specified files by examining their file name extension, e.g. ".gif" or ".ps".  
The command used to determine the MIME type is getmimetype.



NFS on linux
2010-09-03T04:00:00.000+08:00


1. Introduction
 The Network File System is certainly one of the most widely used  network services. Network file system (NFS) is based on the Remote  procedure call. It allows the client to automount and therefore,  transparently access the remote file systems on the network.
 2. Scenario
 In this scenario we are going to export the file system from the  linuxconfig.org (IP address 10.1.1.200) host and mount it on  linuxconfig.local(IP address 10.1.1.100).
 3. Prerequisites
 At this point, we assume that the NFS service daemon is already  installed on your system, including portmap daemon on which  NFS setupt  depends. Moreover, your system needs to support the NFS file system.
  $ cat /proc/filesystems 
 
 
    NFS daemon should be listening on both standard ports 2049 and  portmap on port 111.
 
Another way  to check if NFS is functioning, is to use the rpcinfo command.
 # rpcinfo -p 
 You should get a response/output similar to one below:
 
4. Server export file
 All NFS server exports need to be defined in /etc/exports file.
 4.1. Most common exports  options
 Here are the most common export techniques and options:
    /home/nfs/ 10.1.1.100(rw,sync)  export /home/nfs directory for host with IP 10.1.1.100 with read,  write permissions, and synchronized mode  
  /home/nfs/ 10.1.1.0/24(ro,sync)  export /home/nfs directory for network 10.1.1.0 netmask  255.255.255.0 with read only permissions and synchronized mode  
  /home/nfs/ 10.1.1.100(rw,sync) 10.1.1.10(ro,sync)  export /home/nfs directory for host with IP 10.1.1.100 with read,  write permissions, synchronized mode, and also export /home/nfs  directory for hosts with IP 10.1.1.10 with read only permissions and  synchronized mode  
  /home/nfs/ 10.1.1.100(rw,sync,no_root_squash)  export /home/nfs directory for host with IP 10.1.1.100 with read,  write permissions, synchronized mode and the remote root user will be  treated as a root and will be able to change any file and directory.  
  /home/nfs/ *(ro,sync)  export /home/nfs directory for any host with a read only permission  and synchronized mode  
  /home/nfs/ *.linuxconfig.org(ro,sync)  export /home/nfs directory for any host within linuxconfig.org  domain with a read only permission and synchronized mode  
  /home/nfs/ foobar(rw,sync)  export /home/nfs directory for hostname foobar with read, write  permissions and synchronized mode  
 
 
 4.2. Edit exports file
 Open up your favorite text editor, for example, vim and edit  /etc/exports file and add line /home/nfs/ *(ro,sync) to export /home/nfs  directory for any host with read only permissions. 
 Be sure that the directory you export by NFS exists. You can also  create a file inside the /home/nfs directory which will help you  troubleshoot once you mount this file system remotely.
 # touch /home/nfs/test_file 
 4.3. Restart NFS daemon
 Once you edit /etc/exports file you need to restart NFS daemon to  apply changes in the /etc/exports file. Depending on your Linux  distribution, the restarting of NFS may differ.  Debian users:
 # /etc/init.d/nfs-kernel-server restart 
 Redhat users
 # /etc/init.d/nfs restart 
 If you later decide to add more NFS exports to the /etc/exports file,  you will need to either restart NFS daemon or run command  exportfs:
 # exportfs -ra 
 5. Mount remote file  system on client
 First we need to create a mount point:
 # mkdir /home/nfs_local 
 If you are sure that the NFS client and mount point are ready, you  can run the mount command to mount exported NFS remote file system:
 # mount 10.1.1.200:/home/nfs /home/nfs_local 
 In case that you need to specify a type of the filesystem you can do  this by:
 # mount -t nfs 10.1.1.200:/home/nfs /home/nfs_local 
 You may get error message
 mount: mount to NFS server failed: timed out (retrying). 
 This may mean that your server supports higher versions of nfs and  therefore you need to pass one extra argument to your nfs client. In  this example we use nfs version 3:
 # mount -t nfs -o nfsvers=3 10.1.1.200:/home/nfs /home/nfs_local 
 
 Now you should be able to see that the file system is mounted. Notice  that the mount command reports that the filesystem is mounted as "read  and write", although you can see that it provides a "read only"  permission.
 6. Configure automount
 To make this completely transparent to end users, you can automount  the NFS file system every time a user boots a PC, or you can also use  PAM modules to mount once a user logs in with a proper username and  password. In this situation just edit /etc/fstab to mount system  automatically during a system boot. You can use your favorite editor and  create new line like this:
 10.1.1.200:/home/nfs /home/nfs_local/ nfs defaults 0 0 
 in /etc/fstab or
 # echo "10.1.1.200:/home/nfs /home/nfs_local/ nfs defaults 0 0" >> /etc/fstab 
 



multipathing on linux
2010-09-02T22:45:00.002+08:00


1. check file ni tgk entry ni dah disable ke belum

[server mpath]# more /etc/multipath.conf# Blacklist all devices by default. Remove this to enable multipathing# on the default devices.#devnode_blacklist {# devnode "*"#}

2. buat step ni utk recreate / refresh multipath

[server mpath]# chkconfig multipathd on
[server mpath]# modprobe dm-multipath
[server mpath]# modprobe dm-round-robin
[server mpath]# cd /etc/init.d
[server init.d]# ./multipathd restart


2 step ni utk create multipath


untuk check disk,after restart multipath

1. [server mpath]# ll /dev/mpath
check entry ada tak macam ni

# lltotal 0lrwxrwxrwx 1 root root 7 Jul 15 11:06 [00;36m360060480000190105137533032334630[00m -> [40;33;01m../dm-8[00mlrwxrwxrwx 1 root root 8 Jul 15 11:06 [00;36m360060480000190105137533032343030[00m -> [40;33;01m../dm-10[00mlrwxrwxrwx 1 root root 8 Jun 20 07:02 [00;36mSAN-disk100m -> 40;33;01m../dm-20[00mlrwxrwxrwx 1 root root 8 Jun 20 07:02 [00;36mSAN-disk1000m -> 40;33;01m../dm-23[00m

2 line atas tu disk baru ( belum configure)
2 line yang bawah tu disk lama ( dah configure)


utk tau raw disk ni nnt assign kat mana, check koman ni
# multipath -ll
SAN-disk16 (360060480000190105137533032333130)[size=67 GB][features="0"][hwhandler="0"]\_ round-robin 0 [active] \_ 4:0:0:58 sdax 67:16 [active][ready] \_ 2:0:0:58 sdr 65:16 [active][ready]
SAN-disk15 (360060480000190105137533032353038)[size=67 GB][features="0"][hwhandler="0"]\_ round-robin 0 [active] \_ 4:0:0:49 sdaw 67:0 [active][ready] \_ 2:0:0:49 sdq 65:0 [active][ready]
SAN-disk27 (360060480000190105137533032343030)[size=67 GB][features="0"][hwhandler="0"]\_ round-robin 0 [active] \_ 2:0:0:70 sdad 65:208 [active][ready] \_ 4:0:0:70 sdbj 67:208 [active][ready]
SAN-disk26 (360060480000190105137533032334630)[size=67 GB][features="0"][hwhandler="0"]\_ round-robin 0 [active] \_ 2:0:0:68 sdab 65:176 [active][ready] \_ 4:0:0:68 sdbh 67:176 [active][ready]


so dari situ awak kena matchkan

lrwxrwxrwx 1 root root 7 Jul 15 11:06 [360060480000190105137533032334630 -> [40;33;01m../dm-8[00m
sebenanya sama dengan
SAN-disk26 (360060480000190105137533032334630)[size=67 GB][features="0"][hwhandler="0"]\_ round-robin 0 [active] \_ 2:0:0:68 sdab 65:176 [active][ready] \_ 4:0:0:68 sdbh 67:176 [active][ready]
after tu kena crete disk

ni step utk create disk

# fdisk /dev/sdab Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabelBuilding a new DOS disklabel. Changes will remain in memory only,until you decide to write them. After that, of course, the previouscontent won't be recoverable.
The number of cylinders for this disk is set to 8803.There is nothing wrong with that, but this is larger than 1024,and could in certain setups cause problems with:1) software that runs at boot time (e.g., old versions of LILO)2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK)Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
Command (m for help): p <<<----- check dulu disk dah assign belum. kalau tgk kat sini dia belum assign so boleh proceed Disk /dev/sdab: 72.4 GB, 72414658560 bytes255 heads, 63 sectors/track, 8803 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System Command (m for help): n <<------- n utk newCommand action e extended p primary partition (1-4) p <<------ p untuk primary Partition number (1-4): 1 <<----------- tekan 1 First cylinder (1-8803, default 1): 1Using default value 1Last cylinder or +size or +sizeM or +sizeK (1-8803, default 8803): Using default value 8803 Command (m for help): p <<--------------check balik tgk disk dah assign. tapi system type still linux. kena tuka LVM Disk /dev/sdab: 72.4 GB, 72414658560 bytes255 heads, 63 sectors/track, 8803 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System/dev/sdab 1 8803 70710066 83 Linux Command (m for help): t <<---------- type t untuk tukar (type)Selected partition 1Hex code (type L to list codes): 8e <<------------------ code LVM 8e. nak tgk code lain type lChanged system type of partition 1 to 8e (Linux LVM) Command (m for help): p << ------------------- check balik skang dia dah tuka LVM Disk /dev/sdab: 72.4 GB, 72414658560 bytes255 heads, 63 sectors/track, 8803 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System/dev/sdab 1 8803 70710066 8e Linux LVM Command (m for help): w <<-------------------- ni utk save configurationThe partition table has been altered! Calling ioctl() to re-read partition table.Syncing disks.# lepas tu continue utk disk2 yang lain after create disk semua, buat macam biasa # vgextend VolGroup01 /dev/mpath/SAN-diskxxx ( check SAN-disk kat /dev/mpath) # lvcreate -L 544G /dev/VolGroup01 -n ou08_vol # mkfs -t ext3 -m0 /dev/VolGroup01/ou08_vol # mkdir /oracle/u08 # chown oracle:dba /oracle/u08 # chmod 770 /oracle/u08 # mount /dev/VolGroup01/ou08_vol /oracle/u08 # chmod 770 /oracle/u08 # df -h /oracle/u08 Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup01-ou08_vol 536G 102M 536G 1% /oracle/u08 # vi /etc/fstab If tak jadi try run koman ni : Run command nie echo 1 > /sys/class/fc_host/host/issue_lip
echo "- - -" > /sys/class/scsi_host/host/scan


nk tau ape, ls –lrt under /sys/class/fc_host and /sys/class/scsi_host/. If ade host0, host1, etc, so kene run one by one..
pastu restart service, then nmpk..

[server init.d]# multipath -ll

mpath38 (360060480000290101604533031363238)
[size=67 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [prio=2][active]
\_ 2:0:0:60 sdca 68:224 [active][ready]
\_ 4:0:0:60 sdci 69:96 [active][ready]

mpath40 (360060480000290101604533031363438)
[size=67 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [prio=2][active]
\_ 2:0:0:64 sdce 69:32 [active][ready]
\_ 4:0:0:64 sdcm 69:160 [active][ready]

mpath45 (360060480000290101604533031363230)
[size=67 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [prio=2][active]
\_ 2:0:0:59 sdbz 68:208 [active][ready]
\_ 4:0:0:59 sdch 69:80 [active][ready]

mpath44 (360060480000290101604533031363330)
[size=67 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [prio=2][active]
\_ 2:0:0:61 sdcb 68:240 [active][ready]
\_ 4:0:0:61 sdcj 69:112 [active][ready]

mpath43 (360060480000290101604533031363138)
[size=67 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [prio=2][active]
\_ 2:0:0:58 sdby 68:192 [active][ready]
\_ 4:0:0:58 sdcg 69:64 [active][ready]

mpath42 (360060480000290101604533031363338)
[size=67 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [prio=2][active]
\_ 2:0:0:62 sdcc 69:0 [active][ready]
\_ 4:0:0:62 sdck 69:128 [active][ready]

mpath39 (360060480000290101604533031363430)
[size=67 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [prio=2][active]
\_ 2:0:0:63 sdcd 69:16 [active][ready]
\_ 4:0:0:63 sdcl 69:144 [active][ready]

mpath41 (360060480000290101604533031363130)
[size=67 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [prio=2][active]
\_ 2:0:0:57 sdbx 68:176 [active][ready]
\_ 4:0:0:57 sdcf 69:48 [active][ready]



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

Wahai rakyat jelata sekalian,

Kalau dah buat steps bawah ni tapi disk still tak nampak,
Boleh scan guna cara ni :


Run command nie 
echo 1 > /sys/class/fc_host/host/issue_lip
echo "- - -" > /sys/class/scsi_host/host/scan


nk tau  ape, ls –lrt under /sys/class/fc_host and /sys/class/scsi_host/. If ade host0, host1, etc, so kene run one by one..
pastu restart service, then nmpk..

[root@server init.d]# multipath -ll

mpath38 (360060480000290101604533031363238)
[size=67 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [prio=2][active]
 \_ 2:0:0:60 sdca 68:224 [active][ready]
 \_ 4:0:0:60 sdci 69:96  [active][ready]

mpath40 (360060480000290101604533031363438)
[size=67 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [prio=2][active]
 \_ 2:0:0:64 sdce 69:32  [active][ready]
 \_ 4:0:0:64 sdcm 69:160 [active][ready]

mpath45 (360060480000290101604533031363230)
[size=67 GB][features="0"][hwhandler="0"]
\_ round-robin 0 [prio=2][active]
 \_ 2:0:0:59 sdbz 68:208 [active][ready]
 \_ 4:0:0:59 sdch 69:80  [active][ready]

`-s subject`	Use `subject` for the e-mail title
`-c address`	Send copy of the mail to the specified address
`-b address`	Send blind carbon copy to specified address

-b	batch (non-interactive) mode
-c `cc`	CC address (for copy of the mail)
-f `filename`	Name of file to attach
-m `MIME-type`	MIME content type, e.g. "`text/plain`" or "`application/octet-stream`"
-s `subject`	Title (subject) of the mail message
-t `to`	Recipient's address
-n	Next file attachment (needed for multiple file attachments)
-D `description`	Description of the file content
-o `outputfile`	Name of an output file. If the -t option is given, the mail is sent directly to the addressee

/home/nfs/ 10.1.1.100(rw,sync)	export /home/nfs directory for host with IP 10.1.1.100 with read, write permissions, and synchronized mode
/home/nfs/ 10.1.1.0/24(ro,sync)	export /home/nfs directory for network 10.1.1.0 netmask 255.255.255.0 with read only permissions and synchronized mode
/home/nfs/ 10.1.1.100(rw,sync) 10.1.1.10(ro,sync)	export /home/nfs directory for host with IP 10.1.1.100 with read, write permissions, synchronized mode, and also export /home/nfs directory for hosts with IP 10.1.1.10 with read only permissions and synchronized mode
/home/nfs/ 10.1.1.100(rw,sync,no_root_squash)	export /home/nfs directory for host with IP 10.1.1.100 with read, write permissions, synchronized mode and the remote root user will be treated as a root and will be able to change any file and directory.
/home/nfs/ *(ro,sync)	export /home/nfs directory for any host with a read only permission and synchronized mode
/home/nfs/ *.linuxconfig.org(ro,sync)	export /home/nfs directory for any host within linuxconfig.org domain with a read only permission and synchronized mode
/home/nfs/ foobar(rw,sync)	export /home/nfs directory for hostname foobar with read, write permissions and synchronized mode