1. How much storage (PPs) do I have free.
2.How much storage (PPs) is in use.
3.How much storage (PPs) is actually being used.

I can get the first two questions answered looking at the output of “lsvg”, but the last one I cannot.

Now, lets take a look at the following “lsvg” output:

root@AIX / > lsvg data
VOLUME GROUP:       data                     VG IDENTIFIER:  000771a50000d6000000011bd8f66761
VG STATE:           active                   PP SIZE:        128 megabyte(s)
VG PERMISSION:      read/write               TOTAL PPs:      13410 (1716480 megabytes)
MAX LVs:            256                      FREE PPs:       7729 (989312 megabytes)
LVs:                12                       USED PPs:       5681 (727168 megabytes)
OPEN LVs:           12                       QUORUM:         4
TOTAL PVs:          6                        VG DESCRIPTORS: 6
STALE PVs:          0                        STALE PPs:      0
ACTIVE PVs:         6                        AUTO ON:        yes
MAX PPs per VG:     30480
MAX PPs per PV:     3048                     MAX PVs:        10
LTG size (Dynamic): 256 kilobyte(s)          AUTO SYNC:      no
HOT SPARE:          no                       BB POLICY:      relocatable

“Used PPs” tells us that 727GB has been allocated to filesystems in the “data” volume group. However, the output of a “df -vg” shows that only a little over 250GB is actually being used.

This information is helpful to know when you’re struggling to find space to increase filesystems, or allocate space for a new one. It’s good to know exactly how much a filesystem is consuming of the potential data allocation in the volume group itself, and how much can be taken for other filesystems to fulfill the allocation request.

Unless there is an AIX command which I haven’t stumbled across yet, you need to work all this out by doing the following.

1. Do a “lsvg -l ” to find out which filesystems belong to the volume group.
2. Do a “df -vg” on each of the filesystems to see how much is actually being used.
3. Add all the values together to get the total sum.

Pain in the ass if you ask me, and the resolution is the exact reason why task automation via shell scripting is great.

Here is a script that I wrote called “vgusage”. Put it in /usr/bin and “chmod +x” it.

#!/usr/bin/ksh
#
# Script calculates total usage in a volume group
# and not just space allocated to filesystems.

# Create usage function
usage() {
        echo "USAGE: $0 [k|m|g] [vg]"
}

# Case statement to assign SIZE var
case $1 in
        k)
          SIZE=$1
          SIZEB=KB
          ;;
        m)
          SIZE=$1
          SIZEB=MB
          ;;
        g)
          SIZE=$1
          SIZEB=GB
          ;;
        *)
          usage
          exit 1
          ;;
esac

# Check if $2 exists and assign VG var
if [ -z "$2" ]; then
  usage
  exit 1
else
  VG=$2
fi

# Check that volume group exists
lsvg $VG > /dev/null 2>&1
if [ $? -ne 0 ]; then
  echo "Volume group [$VG] does not exist."
  exit 1
fi

# Create array of all filesystems in volume group
set -A fsname `lsvg -l $VG | awk '{ print $7 }' | awk 'NR!=1' | grep -vE 'LV|N/A'`

# Create array of all filesystem sizes in volume group
count=0
while (( $count < ${#fsname[*]} )); do
           fssize[$count]=`df -v$SIZE "${fsname[$count]}" | awk 'NR!=1' | awk '{ print $3 }'`
        let count="count + 1"
done

# Array loop to print FS and SIZE
count=0
printf "%-30s %s\n" ---------- -------
printf "%-30s %s\n" Filesystem Size-$SIZEB
printf "%-30s %s\n" ---------- -------
while (( $count < ${#fsname[*]} )); do
           printf "%-30s %s\n" ${fsname[$count]} ${fssize[$count]}
        let count="count + 1"
done

# Calculate totals
TOTAL=`echo ${fssize[*]} | awk 'BEGIN {RS=" "} {SUM+=$1} END {print SUM}'`

printf "%-30s %s\n" ----- --------
printf "%-30s %s\n" Total $TOTAL
printf "%-30s %s\n" ----- --------

exit 0

The script takes two parameters. The first being the block value (KB, MB, GB), and the second being the name of the volume group.

root@AIX / > vgusage
USAGE: /usr/bin/vgusage [k|m|g] [vg]

Script being run on the data volume group with the output in GB blocks.

root@AIX / > vgusage g data
----------                     -------
Filesystem                     Size-GB
----------                     -------
/u02                           148.68
/ora/repagg/data01             12.39
/ora/repagg/data02             32.79
/ora/repagg/data03             14.84
/ora/repagg/data04             11.02
/ora/repagg/redo01             0.29
/ora/repagg/redo02             0.29
/app                           0.38
/app/backup                    29.71
/ora/repagg/dat                0.01
/u03                           0.64
-----                          --------
Total                          251.04
-----                          --------

As always, post any questions to the comments.

Below is a simple script which will rotate the last 1000 entries in wtmp and discard the rest.

#!/bin/ksh
#
# Maintain the last 1000 lines in /var/adm/wtmp
# and discard the rest.
#
if [ -s /var/adm/wtmp ]; then
   /usr/sbin/acct/fwtmp < /var/adm/wtmp > /tmp/wtmp.tmp
   /usr/bin/tail -1000 /tmp/wtmp.tmp | /usr/sbin/acct/fwtmp -ic > /var/adm/wtmp
   /usr/bin/rm /tmp/wtmp.tmp
else
   continue
fi

Run it out of crontab nightly or whenever suits you.

I needed to find out quickly which tapes TSM had no knowledge of, and had essentially become scratch. I wrote the following script to do just that for me. You’ll need to tailor it to your environment, as our tapes are bar-coded COL000L4 through to COL120L4.

#!/usr/bin/ksh

dsmadmc="/usr/bin/dsmadmc -id=username -pass=password -dataonly=yes -displ=lis"
count=0
zero=00

echo "The following tapes do not exist in TSM:"
while (( $count <= 120 )); do
        if [ $count -gt 9 ]; then
        let zero=0
        fi

        if [ $count -gt 99 ]; then
        unset zero
        fi

        $dsmadmc q volume ???${zero}${count}?? > /dev/null 2>&1
        if [ $? -ne 0 ]; then
        echo COL${zero}${count}L4
        fi

        let count="count + 1"

done
exit

#!/usr/bin/ksh
#
# This script reports filesystem usages for
# all mounted filesystems.
#
# Filesystems can be excluded by editing the
# SKIPFS variable e.g. SKIPFS='/proc|/test|/home'

MAIL=/usr/bin/mail
RCPT='your@email.com'
USAGE=80
HOSTNAME=`hostname`
SKIPFS='/proc|/test'

set -A fs `df -k | grep -vE $SKIPFS | awk '{ print $4 }' | awk 'NR!=1' | sed 's/%//'`
set -A fn `df -k | grep -vE $SKIPFS | awk '{ print $7 }' | awk 'NR!=1'`

count=0
while (( $count < ${#fs[*]} )); do
        fssize=${fs[$count]}
        if
                [ $fssize -ge $USAGE ]; then
                echo "${fn[$count]} on $HOSTNAME is at ${fssize}%" | $MAIL -s "WARNING on $HOSTNAME" $RCPT
        fi
        let count="count + 1"
done

exit

#!/usr/bin/ksh
# This script monitors various filesystems and emails
# notifications when they hit a set limit
#
MAILTO='your@email.com'
HOSTNAME=`hostname`

ROOT=`df -k|grep "/dev/hd4"|awk '{print $4}'|sed "s/%//"`
USR=`df -k|grep "/dev/hd2"|awk '{print $4}'|sed "s/%//"`
VAR=`df -k|grep "/dev/hd9var"|awk '{print $4}'|sed "s/%//"`
HOME=`df -k|grep "/dev/hd1"|grep -v opt|awk '{print $4}'|sed "s/%//"`
OPT=`df -k|grep "/opt"|awk '{print $4}'|sed "s/%//"`
TMP=`df -k|grep "/dev/hd3"|awk '{print $4}'|sed "s/%//"`

if [ $ROOT -gt 79 ]
then
   echo "We have hit ${ROOT}% on / on $HOSTNAME"|mailx -s "WARNING on $HOSTNAME" $MAILTO
fi
if [ $USR -gt 79 ]
then
   echo "We have hit ${USR}% on /usr on $HOSTNAME"|mailx -s "WARNING on $HOSTNAME" $MAILTO
fi
if [ $VAR -gt 79 ]
then
   echo "We have hit ${VAR}% on /var on $HOSTNAME"|mailx -s "WARNING on $HOSTNAME" $MAILTO
fi
if [ $HOME -gt 79 ]
then
   echo "We have hit ${HOME}% on /home on $HOSTNAME"|mailx -s "WARNING on $HOSTNAME" $MAILTO
fi
if [ $OPT -gt 79 ]
then
   echo "We have hit ${OPT}% on /opt on $HOSTNAME"|mailx -s "WARNING on $HOSTNAME" $MAILTO
fi
if [ $TMP -gt 79 ]
then
   echo "We have hit ${TMP}% on /tmp on $HOSTNAME"|mailx -s "WARNING on $HOSTNAME" $MAILTO
fi

exit

The above script is running on an AIX operating environment, so you’ll need to modify the variables to suit. It’s not all that far to figure out, but if you need a hand…shout out.

There always comes a time, where you wish that file was only a few kilobytes/megabytes smaller. Whether it be so it can fit onto your floppy disk, CD-R etc, or so you can meet the attachment limit on an e-mail server. This isn’t really a command that you would use everyday, but it might come in handy.

Splitting the file

kristijan@slackware testing$ ls -lh
total 13M
-rw-rw-r--  1 kristijan users 13M Jul 23 18:18 karaoke.mp3

Just say we wanted to e-mail this file to a friend, but the e-mail server only allowed a maximum of 2MB attachments.

(Note** I like to play safe, so I will make my chunks of data 1.9M)

1.9 x 1024 = 1945.6

(Note** To play safe once again, I will leave out the decimal and just use 1945)

The command that we will use is:

kristijan@slackware testing$ split -b 1945k karaoke.mp3

kristijan@slackware testing$ split -b 1945k karaoke.mp3
kristijan@slackware testing$ ls -lh
total 26M
-rw-rw-r--  1 kristijan users  13M Jul 23 18:18 karaoke.mp3
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xaa
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xab
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xac
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xad
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xae
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xaf
-rw-rw-r--  1 kristijan users 1.4M Jul 23 18:22 xag

OK, what we have now done is told ’split’ to use bytes per output file (-b). For more information and arguments on split, view the man pages (man split). Split how now ’split’ karaoke.mp3 into 7 smaller files named ‘xaa’, ‘xab’, ‘xac’ etc, which are all under 2M in size.

These files now meet the e-mail server’s attachment limit and can be sent.

Recreating the file (cat)

Recreation of the karaoke.mp3 is even easier. For this, we will be using ‘cat’. See the man pages for more information on ‘cat’ (man cat).

The command that we will use is:

kristijan@slackware testing$ cat xa* > karaoke-restored.mp3

(Note** Before removing the original file, I recommend that you make a backup of it)

kristijan@slackware testing$ rm karaoke.mp3
kristijan@slackware testing$ ls -lh
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xaa
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xab
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xac
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xad
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xae
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xaf
-rw-rw-r--  1 kristijan users 1.4M Jul 23 18:22 xag
kristijan@slackware testing$ cat xa* > karaoke-restored.mp3
kristijan@slackware testing$ ls -lh
total 26M
-rw-rw-r--  1 kristijan users  13M Jul 23 18:39 karaoke-restored.mp3
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xaa
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xab
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xac
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xad
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xae
-rw-rw-r--  1 kristijan users 1.9M Jul 23 18:22 xaf
-rw-rw-r--  1 kristijan users 1.4M Jul 23 18:22 xag

By using cat, we have now recreated the original file. The ‘xaa’, xab’ etc files may now be deleted.

There we have it, the karaoke file is now restored and can be played as per normal.

I had access to a Red Hat AS4 server, so I wrote a shell script to read all the hostnames of the workstations from a text file, mount each C$ share via CIFS, copy the necessary files, unmount and repeat.

Over the past few weeks, I added a few other things which I were of use (ping check prior to send, file verification on remote workstation).

#!/bin/bash
#
# Script to send files to Windows workstations

# set -x

function runPingCheck ()
{
	grep -vE '^$|^#' callcentres/$name.txt | while read i
        do ping -c 1 `echo $i | awk '{print $1}'`.fqdn.com &> /dev/null
                if [ $? -gt 0 ]; then
                        echo -e "$i ... PING FAIL"
                fi

        done
	echo ""
	echo "Check complete"
	echo ""
	echo -n "Continue with send(Y/N) [Y]? "
	read contsend
		case "$contsend" in
			N|n) exit 1 ;;
			Y|y|*) runSendFiles ;;
		esac
}

function runSendFiles ()
{
	echo "Send started `date`" | tee -a $name.log

	grep -vE '^$|^#' callcentres/$name.txt | while read i
        do ping -c 1 `echo $i | awk '{print $1}'`.fqdn.com &> /dev/null
                if [ $? -gt 0 ]; then
                        echo "$i ... Host Offline" | tee -a $name.log
                        continue
                fi

                mount -t cifs //`echo $i | awk '{print $1}'`.fqdn.com/c$ /mnt/winmnt -o user=administrator,pass=PASSHERE
                if [ $? -gt 0 ]; then
                        echo "$i ... Failed CIFS Mount" | tee -a $name.log
                else
                        cp -R ./files/* /mnt/winmnt
                                if [ -e /mnt/winmnt/sent.tmp ]; then
                                        rm /mnt/winmnt/sent.tmp
                                        umount /mnt/winmnt
                                        echo "$i ... Complete" | tee -a $name.log
                                else
                                        umount /mnt/winmnt
                                        echo "$i ... Failed File Verification" | tee -a $name.log
                                fi
                fi
        done

	echo "Send completed `date`" | tee -a $name.log
}

ls ./callcentres | sed 's/.txt//g'
echo ""
echo -n "Type the name of the call centre you wish to upgrade: "
read name

echo ""
echo -n "Would you like to run a ping check before you send(Y/N) [Y]? "
read pingcheck

case "$pingcheck" in
	N|n) runSendFiles ;;
	Y|y|*) runPingCheck ;;
esac

exit 0

The basic directory structure looks like this:
/callcentres
– melbourne.txt
/files
/sendscript.sh

melbourne.txt just had a list of all the hostnames, each on its own line. (# can be used at the start of any line to skip a particular workstation).

host1
#host2
host3
...
host100

/files contains any file that you want to send to the remote Windows host. Take note that you need to provide the absolute path of the Windows location (e.g. /files/Program Files/)

Output of the script will be logged to STDOUT and to a log file in the root directory where sendscript.sh resides.

Once you have the file structure and sendscript.sh in order, simply run the script. You will be prompted for the name of the “call centre” you wish to send files to. In this example, you would enter melbourne. Then you will be asked if you’d like to run a ping check on each workstation prior to the file send.

Happy sending

17 episodes, each in their own folder in .rar files.
What a pain in the ass!

Instead of clicking away at each RAR file individually, I put together a little bash script to do the work for me which I’ve called unrar_all.

#!/bin/bash
#
# Script to unrar season packs of TV shows
# Put it in the directory containing all the directorys
#
# eg.
#       Big_Bang_Theory.1x01.Pilot.DVDRip_XviD-FoV/
#       Big_Bang_Theory.1x02.The_Big_Bran_Hypothesis.DVDRip_XviD-FoV/
#       Big_Bang_Theory.1x03.The_Fuzzy_Boots_Corollary.DVDRip_XviD-FoV/
#       unrar_all

find . -type d -print | while read i
        do pushd .
        cd $i
                unset partrar
                partrar=`find . -name *part01.rar`
                if [ -n "$partrar" ]; then
                unrar e *part01.rar
                mv *.avi ../
                popd
        else
                unrar e *.rar
                mv *.avi ../
                popd
        fi
done

This script requires unrar from RARLabs.