My Job As Sys Admin

Growing a RAID5 array – MDADM

2010-10-21T05:38:00.000-07:00

In this example, I've created a RAID-5(/dev/sdc1,sdd1,sde1) array with LVM

fdisk /dev/sdc
fdisk /dev/sdd
fdisk /dev/sde - create 5G partition with fd (raid)
partprobe /dev/sd[c,d,e]
mdadm --create --verbose /dev/md1 --level=5 --raid-devices=3 /dev/sdc1 /dev/sdd1 /dev/sde1
cat /proc/mdstat
pvcreate /dev/md1
pvdisplay
vgcreate vg00 /dev/md1
vgdisplay
lvcreate -L 2000M -n data1_raid5 /dev/vg00
lvdisplay
mkdir /data1_raid5
mke2fs /dev/vg00/data1_raid5
tune2fs -j /dev/vg00/data1_raid5
mount -t ext3 /dev/vg00/data_raid5 /data1_raid5/
dd if=/dev/zero of=bigfile bs=1024M count=1
lvextend +8G /dev/vg00/data1_raid5
lvdisplay
resize2fs /dev/vg00/data1_raid5
df -h

Growing a RAID5 array – MDADM

With the release of kernel 2.6.17, there’s new functionality to add a device (partition) to a RAID 5 array and make this new device part of the actual array rather than a spare.

creating a new RAID partition /dev/sdf1

mdadm --manage /dev/md1 --add /dev/sdf1
mdadm --detail /dev/md1
mdadm --grow /dev/md1 --raid-devices=4
cat /proc/mdstat

(reshaping is taking in place...)
cat /proc/mdstat
pvdisplay
pvresize /dev/md1
pvdisplay
vgdisplay
now the newly added partition will be the part of RAID5 array and available for extend.
lvextend -L +3G /dev/vg00/data1_raid5

that extended LV few more gigs,,,

that'sall

mdadm: A Tool For Linux Software RAID Management

2010-10-17T00:50:00.000-07:00

Raidtools has been the standard software RAID management package for Linux since the inception of the software RAID driver. Over the years, raidtools have proven cumbersome to use, mostly because they rely on a configuration file (/etc/raidtab) that is difficult to maintain, and partly because its features are limited. In August 2001, Neil Brown, a software engineer at the University of New South Wales and a kernel developer, released an alternative. His mdadm (multiple devices admin) package provides a simple, yet robust way to manage software arrays.

mdadm has five major modes of operation. The first two modes, Create and Assemble, are used to configure and activate arrays. Manage mode is used to manipulate devices in an active array. Follow or Monitor mode allows administrators to configure event notification and actions for arrays. Build mode is used when working with legacy arrays that use an old version of the md driver. I will not cover build mode in this article. The remaining options are used for various housekeeping tasks and are not attached to a specific mode of operation, although the mdadm documentation calls these options Misc mode. mdadm by default comes with the newer versions of Red hat Linux. Alternately, you can download one from,

ftp://ftp.kernel.org/pub/linux/utils/raid/mdadm/

Creating an Array:

Create (mdadm --create) mode is used to create a new array. In this example I use mdadm to create a RAID-0 at /dev/md0 made up of /dev/sdb1 and /dev/sdc1

#mdadm --create --verbose /dev/md0 --level=0 --raid-devices=2 /dev/sdb1 /dev/sdbc1

The --level option specifies which type of RAID to create. Valid choices are 0,1,4 and 5 for RAID-0, RAID-1, RAID-4, RAID-5 respectively. Linear (--level=linear) is also a valid choice for linear mode.

In general, mdadm commands take the format:

mdadm [mode] [options]

Each of mdadm's options also has a short form that is less descriptive but shorter to type. For example, the following command uses the short form of each option but is identical to the example I showed above,

#mdadm -Cv /dev/md0 -l0 -n2 -c128 /dev/sdb1 /dev/sdc1

C selects Create mode, and I have also included the -v option here to turn on verbose output. -l and -n specify the RAID level and number of member disks.You can change the default chunk size (64KB) using the --chunk or -c option. In this previous example I changed the chunk size to 128KB. mdadm also supports shell expansions, so you don't have to type in the device name for every component disk if you are creating a large array. In this example, I'll create a RAID-5 with five member disks and a chunk size of 128KB:

#mdadm -Cv /dev/md0 -l5 -n5 -c128 /dev/sd{a,b,c,d,e}1
mdadm: layout defaults to left-symmetric
mdadm: array /dev/md0 started.

This example creates an array at /dev/md0 using SCSI disk partitions /dev/sda1, /dev/sdb1, /dev/sdc1, /dev/sdd1, and /dev/sde1. Notice that I have also set the chunk size to 128 KB using the -c128 option. When creating a RAID-5, mdadm will automatically choose the left-symmetric parity algorithm, which is the best choice

Use the --stop or -S command to stop running array:
#mdadm -S /dev/md0

/etc/mdadm.conf:

/etc/mdadm.conf is mdadms' primary configuration file. Unlike /etc/raidtab, mdadm does not rely on /etc/mdadm.conf to create or manage arrays. Rather, mdadm.conf is simply an extra way of keeping track of software RAIDs. Using a configuration file with mdadm is useful, but not required. Having one means you can quickly manage arrays without spending extra time figuring out what array properties are and where disks belong. For example, if an array wasn't running and there was no mdadm.conf file describing it, then the system administrator would need to spend time examining individual disks to determine array properties and member disks.

Unlike the configuration file for raidtools, mdadm.conf is concise and simply lists disks and arrays. The configuration file can contain two types of lines each starting with either the DEVICE or ARRAY keyword. Whitespace separates the keyword from the configuration information. DEVICE lines specify a list of devices that are potential member disks. ARRAY lines specify device entries for arrays as well as identifier information. This information can include lists of one or more UUIDs, md device minor numbers, or a listing of member devices.

A simple mdadm.conf file might look like this:

DEVICE /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1
ARRAY /dev/md0 devices=/dev/sda1,/dev/sdb1
ARRAY /dev/md1 devices=/dev/sdc1,/dev/sdd1

In general, it's best to create an /etc/mdadm.conf file after you have created an array and update the file when new arrays are created. Without an /etc/mdadm.conf file you'd need to specify more detailed information about an array on the command in order to activate it.That means you'd have to remember which devices belonged to which arrays, and that could easily become a hassle on systems with a lot of disks. mdadm even provides an easy way to generate ARRAY lines. The output is a single long line, but I have broken it here to fit the page:

# mdadm --detail --scan
ARRAY /dev/md0 level=raid0 num-devices=2 \
UUID=410a299e:4cdd535e:169d3df4:48b7144a

If there were multiple arrays running on the system, then mdadm would generate an array line for each one. So after you're done building arrays you could redirect the output of mdadm --detail --scan to /etc/mdadm.conf. Just make sure that you manually create a DEVICE entry as well. Using the example I've provided above we might have an /etc/mdadm.conf that looks like:

DEVICE /dev/sdb1 /dev/sdc1
ARRAY /dev/md0 level=raid0 num-devices=2 \
UUID=410a299e:4cdd535e:169d3df4:48b7144a

Starting an Array:

Assemble mode is used to start an array that already exists. If you created an /etc/mdadm.conf you can automatically start an array listed there with the following command:

#mdadm -As /dev/md0
mdadm: /dev/md0 has been started with 2 drives

The -A option denotes assemble mode. You can also use --assemble. The -s or --scan option tells mdadm to look in /etc/mdadm.conf for information about arrays and devices. If you want to start every array listed in /etc/mdadm.conf, don't specify an md device on the command line

#mdadm -As

If you didn't create an /etc/mdadm.conf file, you will need to specify additional information on the command line in order to start an array. For example, this command attempts to start /dev/md0 using the devices listed on the command line:

#mdadm -A /dev/md0 /dev/sdb1 /dev/sdc1

Since using mdadm -A in this way assumes you have some prior knowledge about how arrays are arranged, it might not be useful on systems that have arrays that were created by someone else. So you may wish to examine some devices to gain a better picture about how arrays should be assembled. The examine options (-E or --examine) allows you to print the md superblock (if present) from a block device that could be an array component.

#mdadm -E /dev/sdc1
/dev/sdc1:
Magic : a92b4efc
Version : 00.90.00
UUID : 84788b68:1bb79088:9a73ebcc:2ab430da
Creation Time : Mon Sep 23 16:02:33
Raid Level : raid0
Device Size : 17920384 (17.09 GiB 18.40 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0

Update Time : Mon Sep 23 16:14:52 2002
State : clean, no-errors
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : 8ab5e437 - correct
Events : 0.10

Chunk Size : 128K

Number Major Minor RaidDevice State
this 1 8 33 1 active sync /dev/sdc1
0 0 8 17 0 active sync /dev/sdb1
1 1 8 33 1 active sync /dev/sdc1
2 2 8 49 2 active sync /dev/sdd1
3 3 8 65 3 active sync /dev/sde1

mdadm's examine option displays quite a bit of useful information about component disks. In this case we can tell that /dev/sdc1 belongs to a RAID-0 made up of a total of four member disks. What I want to specifically point out is the line of output that contains the UUID. A UUID is a 128-bit number that is guaranteed to be reasonably unique on both the local system and across other systems. It is a randomly generated using system hardware and timestamps as part of its seed. UUIDs are commonly used by many programs to uniquely tag devices. See the uuidgen and libuuid manual pages for more information.

When an array is created, the md driver generates a UUID for the array and stores it in the md superblock. You can use the UUID as criteria for array assembly. In the next example I am going to activate the array to which /dev/sdc1 belongs using its UUID

#mdadm -Av /dev/md0 --uuid=84788b68:1bb79088:9a73ebcc:2ab430da /dev/sd*

This command scans every SCSI disk (/dev/sd*) to see if it's a member of the array with the UUID 84788b68:1bb79088:9a73ebcc:2ab430da and then starts the array, assuming it found each component device. mdadm will produce a lot of output each time it tries to scan a device that does not exist. You can safely ignore such warnings.

Managing Arrays
Using Manage mode you can add and remove disks to a running array. This is useful for removing failed disks, adding spare disks, or adding replacement disks. Manage mode can also be used to mark a member disk as failed.

For example, to add a disk to an active array,

#mdadm /dev/md0 --add /dev/sdc1

Or, to remove /dev/sdc1 from /dev/md0 try

#mdadm /dev/md0 --fail /dev/sdc1 --remove /dev/sdc1

Notice that I first mark /dev/sdc1 as failed and then remove it. It's fine to combine add, fail, and remove options on a single command line as long as they make sense in terms of array management. So you have to fail a disk before removing it, for example.

Monitoring Arrays:

Follow, or Monitor, mode provides some of mdadm's best and most unique features. Using Follow/Monitor mode you can daemonize mdadm and configure it to send email alerts to system administrators when arrays encounter errors or fail. You can also use Follow mode to arbitrarily execute commands when a disk fails. For example, you might want to try removing and reinserting a failed disk in an attempt to correct a non-fatal failure without user intervention.

The following command will monitor /dev/md0 (polling every 300 seconds) for critical events. When a fatal error occurs, mdadm will send an email to sysadmin. You can tailor the polling interval and email address to meet your needs.

# mdadm --monitor --mail=sysadmin --delay=300 /dev/md0

When using monitor mode, mdadm will not exit, so you might want to wrap it around nohup and ampersand:

# nohup mdadm --monitor --mail=sysadmin --delay=300 /dev/md0 &

Follow/Monitor mode also allows arrays to share spare disks, a feature that has been lacking in Linux software RAID since its inception. That means you only need to provide one spare disk for a group of arrays or for all arrays. It also means that system administrators don't have to manually intervene to shuffle around spare disks when arrays fail. Previously this functionality was available only using hardware RAID. When Follow/Monitor mode is invoked, it polls arrays at regular intervals. When a disk failure is detected on an array without a spare disk, mdadm will remove an available spare disk from another array and insert it into the array with the failed disk. To facilitate this process, each ARRAY line in /etc/mdadm.conf needs to have a spare-group defined.

DEVICE /dev/sd*
ARRAY /dev/md0 level=raid1 num-devices=3 spare-group=database \
UUID=410a299e:4cdd535e:169d3df4:48b7144a
ARRAY /dev/md1 level=raid1 num-device=2 spare-group=database \
UUID=59b6e564:739d4d28:ae0aa308:71147fe7

In this example, both /dev/md0 and /dev/md1 are part of the spare group database. Just assume that /dev/md0 is a two-disk RAID-1 with a single spare disk. If mdadm is running in monitor mode (as I showed earlier), and a disk in /dev/md1 fails, mdadm will remove the spare disk from /dev/md0 and insert it into /dev/md1.

Here is the actual testing I did:
================================

Created a raid 1 array with two devices (/dev/sda8, /dev/sdb1) of 10GB each.

[root@lnx-rhel5-vm ~]# fdisk /dev/sda

The number of cylinders for this disk is set to 2610.
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)

Command (m for help): p

Disk /dev/sda: 21.4 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 16 128488+ 83 Linux
/dev/sda2 17 408 3148740 83 Linux
/dev/sda3 409 800 3148740 83 Linux
/dev/sda4 801 2610 14538825 5 Extended
/dev/sda5 801 1061 2096451 83 Linux
/dev/sda6 1062 1192 1052226 83 Linux
/dev/sda7 1193 1323 1052226 82 Linux swap / Solaris
/dev/sda8 1324 2540 9775521 fd Linux raid autodetect

[root@lnx-rhel5-vm ~]# fdisk /dev/sdb

The number of cylinders for this disk is set to 1435.
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)

Command (m for help): p

Disk /dev/sdb: 11.8 GB, 11811160064 bytes
255 heads, 63 sectors/track, 1435 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 1217 9775521 fd Linux raid autodetect

#partprobe /dev/sda
#partprobe /dev/sdb

Creating an arry,
----------------

#mdadm --create --verbose /dev/md0 --level=1 --raid-devices=2 /dev/sda8 /dev/sdb1

This process will take some time to build an raid-1 and then execute to see the status,

[root@lnx-rhel5-vm ~]# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sdb1[1] sda8[0]
9775424 blocks [2/2] [UU]

unused devices:

Creating a File system,

#mkfs.ext3 /dev/md0
#mkdir /raid1

Mounting,
#mount -t ext3 /dev/md0 /raid1

[root@lnx-rhel5-vm ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 3.0G 273M 2.5G 10% /
/dev/sda6 996M 73M 872M 8% /var
/dev/sda5 2.0G 36M 1.9G 2% /home
/dev/sda2 3.0G 2.0G 838M 71% /usr
/dev/sda1 122M 12M 105M 10% /boot
tmpfs 252M 0 252M 0% /dev/shm
/dev/md0 9.2G 159M 8.6G 2% /raid1

[root@lnx-rhel5-vm ~]# mdadm --detail /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Wed Oct 20 02:02:46 2010
Raid Level : raid1
Array Size : 9775424 (9.32 GiB 10.01 GB)
Used Dev Size : 9775424 (9.32 GiB 10.01 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent

Update Time : Wed Oct 20 02:36:56 2010
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

UUID : c42a6efb:849197a4:4935bd46:a423f66f
Events : 0.40

Number Major Minor RaidDevice State
0 8 8 0 active sync /dev/sda8
1 8 17 1 active sync /dev/sdb1

Now, we can copy some data into /raid1 and then fail the one of the device (/dev/sdb1) in array to see if it works,

Failing a disk or partition on array,

[root@lnx-rhel5-vm raid1]# mdadm --manage /dev/md0 --fail /dev/sda8
mdadm: set /dev/sda8 faulty in /dev/md0

[root@lnx-rhel5-vm raid1]# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sdb1[1] sda8[2](F)
9775424 blocks [2/1] [_U]

unused devices:

Above [_U] means, one of the disk is in failed state.

[root@lnx-rhel5-vm raid1]# mdadm --detail /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Wed Oct 20 02:02:46 2010
Raid Level : raid1
Array Size : 9775424 (9.32 GiB 10.01 GB)
Used Dev Size : 9775424 (9.32 GiB 10.01 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent

Update Time : Wed Oct 20 02:40:03 2010
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 1
Spare Devices : 0

UUID : c42a6efb:849197a4:4935bd46:a423f66f
Events : 0.42

Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 17 1 active sync /dev/sdb1

2 8 8 - faulty spare /dev/sda8

You could also see the disk failure messages in /var/log/messages:

#tail /var/log/messages

Oct 20 02:39:43 lnx-rhel5-vm kernel: md: cannot remove active disk sda8 from md0 ...
Oct 20 02:40:03 lnx-rhel5-vm kernel: raid1: Disk failure on sda8, disabling device.
Oct 20 02:40:03 lnx-rhel5-vm kernel: Operation continuing on 1 devices
Oct 20 02:40:03 lnx-rhel5-vm kernel: RAID1 conf printout:
Oct 20 02:40:03 lnx-rhel5-vm kernel: --- wd:1 rd:2
Oct 20 02:40:03 lnx-rhel5-vm kernel: disk 0, wo:1, o:0, dev:sda8
Oct 20 02:40:03 lnx-rhel5-vm kernel: disk 1, wo:0, o:1, dev:sdb1
Oct 20 02:40:03 lnx-rhel5-vm kernel: RAID1 conf printout:
Oct 20 02:40:03 lnx-rhel5-vm kernel: --- wd:1 rd:2
Oct 20 02:40:03 lnx-rhel5-vm kernel: disk 1, wo:0, o:1, dev:sdb1

Now, we are going to remove the failed disk from the array,

[root@lnx-rhel5-vm raid1]# mdadm --manage /dev/md0 --remove /dev/sda8
mdadm: hot removed /dev/sda8
[root@lnx-rhel5-vm raid1]# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sdb1[1]
9775424 blocks [2/1] [_U]

unused devices:

Check the status after removal,

[root@lnx-rhel5-vm raid1]# mdadm --detail /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Wed Oct 20 02:02:46 2010
Raid Level : raid1
Array Size : 9775424 (9.32 GiB 10.01 GB)
Used Dev Size : 9775424 (9.32 GiB 10.01 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent

Update Time : Wed Oct 20 02:41:20 2010
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0

UUID : c42a6efb:849197a4:4935bd46:a423f66f
Events : 0.44

Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 17 1 active sync /dev/sdb1

You can just shutdown the server and pull the failed disk and replaced with the brand new disk of same size. Once the server back online, issue the following command to add new disk under raid array,

[root@lnx-rhel5-vm raid1]# mdadm --manage /dev/md0 --add /dev/sda8
mdadm: re-added /dev/sda8

[root@lnx-rhel5-vm raid1]# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sda8[0] sdb1[1]
9775424 blocks [2/1] [_U]
[>....................] recovery = 1.0% (98752/9775424) finish=6.5min speed=24688K/sec

unused devices:

As you can see above, the reconstruction of array has started working after adding a new one.

References,
http://www.gagme.com/greg/linux/raid-lvm.php
http://scotgate.org/2006/07/03/growing-a-raid5-array-mdadm/
http://lkml.org/lkml/2006/3/20/105

How to connect VM's from a host OS

2010-10-02T03:46:00.000-07:00

This procedure was tested on VMware workstation 6.0 under Windows 7 (Dell Latitude laptop).

1. Install VMware workstation on Window 7.
2. Set up a Bridged Network and create a VM or two VM's of Red Hat Linux 5.2

These VMs having the IP addresses of,
1st VM - 192.168.0.1
2nd VM - 192.168.0.2

Once they have installed and configured, you can connect both the VM through their Linux terminal konsole. So you can ping and SSH them vice versa.

3. Now, you would like to connect these VM's from a host machine (windows 7) through a software called PuTTY. In order to do so, you would need to set up a Windows Loop back Adapter and configure the IP address as 192.168.0.3 ( of a same VM's sub net).

To install a Microsoft Loopback adapter in WIndows 7,

1. Click Start – Search for cmd, right-click cmd and select “Run as Administrator”
2. From the command prompt, run “hdwwiz.exe“. This should launch the “Add Hardware Wizard“
3. Select “Install the hardware that I manually select from a list (Advanced)” and click Next.
4. Now from the list select Network Adapters and click Next
5. Under Manufacturers, select Microsoft and select “Microsoft Loopback Adapter” under Network Adapter and click Next. This should start the installation. Click Finish when the installation completes.

To confirm the loopback adapter installed, right-click Computer, select properties. Click Device Manager and expand Network Adapters and you can see the Loopback adapter installed there. Now, configure a new IP for this network as 192.168.0.3

Once its done, try ping to any of your VM (ex, 192.168.0.1) and check if you're able to ping. If it works, you can then connect using puTTy. Isn't so kool.

Kernel Panic and system hang senarios

2009-09-08T22:49:00.001-07:00

Kernel Panic and system hang senarios
=====================================

If you are using 64 bit AMD/Intel EM64T based kerne. Then, many servers have problem to boot 64bit SMP servers so boot into single UP mode server. Type following two parameters at Grub prompt

Code:

nosmp maxcpu=1

In addition, boot system into single UP mode then update your kernel and try it out again.

You need to enter nosmp and maxcpus parameter at Grub or Lilo boot prompt. For example if you are using Grub as a boot loader, at Grub prompt press 'e' to edit command before booting.

1) Select second line
2) Again, press 'e' to edit selected command
3) Go to end of line and type two parameters

nosmp maxcpu=1

4) Press enter twice and b to boot system
5) This will prevent the kernel panic and system hang scenario.

Once your system is up using single CPU then you can run diagnostic commands such as:

Get all boot message:

dmesg | less

Find out problem with PCI cards

lspci

Find out what device drivers loaded (if something is missing then your driver will not get loaded)

lsmod

Get memory info (is memory detected correctly?)

free
cat /proc/meminfo

Get CPU info (see if your CPU hit by any bug):

top
cat /proc/cpuinfo

Find out kernel version

uname -a

JAVA OUT OF MEMORY ERROR

2009-09-08T22:48:00.000-07:00

:::JAVA OUT OF MEMORY ERROR::::
==========================================================================================

05:35:34,193 ERROR [[/embarqcc].[jsp]] Servlet.service() for servlet jsp threw exception
java.lang.OutOfMemoryError

This issue seems not related to the OS and it related to setting up Java VM pool settings. In your JBoss file, you need to specify the Java VM memory allocation pool parameters as per your requirement. Please recheck them once.

Go to your JBOSS run.bat or run.sh file,

check for JAVA_OPTS, you find this

rem Sun JVM memory allocation pool parameters. Modify as appropriate.
set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m

here Xms128m is the minimum java memory allocated and it go up to max 512m and you can increase this value if your hardware supports according to java specs

Install Mysql Server on Windows

2009-09-08T22:47:00.001-07:00

Install Mysql Server on Windows:

when you receive following error while installing mysql on windows:

"Cannot Create Windows Service for MySQL. Error:0"

What you need to do is to open command line (Start -> Run -> cmd) and type the following:

sc delete mysql

You should receive a message like this:

[SC] DeleteService SUCCESS

Then uninstall MySQL completely using "Add or Remove Programs". After it has been uninstalled, install it again using installation wizard. When it ends, don't choose to configure MySQL right away, instead just uncheck the box and click OK.

Open command line (Start -> Run -> cmd) and type this:

C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt.exe --install MySQL50 --defaults-file="C:\Program Files\MySQL\MySQL Server 5.0\bin\my.ini"

Note: 'MySQL50' is the name of the MySQL service and it needs to be different than 'MySQL'.

Hit enter and restart your Mysql service by going to Admin tools --> services. MySQL should be running fine now.

To work mysql, go to cmd and type:

mysql -u root -p
password: just hit enter

To make mysql binary to your path do this,

Right click on My computer >> Properties >> Advanced >> Environment Variables >> click on path and edit >> add the path

C:\Program Files\MySQL\MySQL Server 5.0\bin

or

under system variables >> click on new

mysql
C:\Program Files\MySQL\MySQL Server 5.0\bin

click ok...

Installing Perl Modules using CPAN

2009-09-08T22:46:00.000-07:00

There are several ways to get Perl modules from CPAN installed on your unix-based system. Keep in mind that there is always more than one way to do it with Perl, and this is no different. Before embarking upon any installation, it's a good idea to download the module, unzip it and check out the documentation. In general, though, most modules are installed in the same method.
The simplest way to get Perl modules installed is to use the CPAN module itself. If you are the system administrator and want to install the module system-wide, you'll need to switch to your root user. To fire up the CPAN module, just get to your command line and run this:

perl -MCPAN -e shell

If this is the first time you've run CPAN, it's going to ask you a series of questions - in most cases the default answer is fine. Once you find yourself staring at the cpan> command prompt, installing a module is as easy as install MODULE::NAME - for example, to install the HTML::Template module you'd type:

cpan> install HTML::Template

CPAN should take it from there and you'll wind up with the module installed into your Perl library.
Let's say you're on your system command line and you just want to install a module as quickly as possible - you can run the Perl CPAN module via command line perl and get it installed in a single line:

perl -MCPAN -e 'install HTML::Template'

As I mentioned earlier, it's always advisable to download a module yourself, especially if you're having problems installing with CPAN. If you're on the command line, you can use something like wget to grab the file. Next you'll want to unzip it with something like:

tar -zxvf HTML-Template-2.8.tar.gz

This will unzip the module into a directory, then you can move in and poke around - look for the README or INSTALL files. In most cases, installing a module by hand is still pretty easy, though (although not as easy as CPAN). Once you've switched into the base directory for the module, you should be able to get it installed by typing:

perl Makefile.PL
make
make test
make install

Installing a BASH shell on HP-UX - PA-RISC 11.23

2009-09-08T22:45:00.001-07:00

Installing a BASH shell on HP-UX - PA-RISC 11.23

Please go to this site and download the BASH shell and it's dependencies,

http://hpux.cs.utah.edu/hppd/cgi-bin/search?package=on&description=on&term=bash&Search=Search
http://hpux.cs.utah.edu/hppd/cgi-bin/redirect?hpux/Shells/bash-3.2/bash-3.2-hppa-11.23.depot.gz

Depedencies,

libiconv:
http://hpux.cs.utah.edu/hppd/cgi-bin/redirect?hpux/Development/Libraries/libiconv-1.12/libiconv-1.12-hppa-11.23.depot.gz

gettext:
http://hpux.cs.utah.edu/hppd/cgi-bin/redirect?hpux/Gnu/gettext-0.17/gettext-0.17-hppa-11.23.depot.gz

termcap:
http://hpux.cs.utah.edu/hppd/cgi-bin/redirect?hpux/Development/Libraries/termcap-1.3.1/termcap-1.3.1-hppa-11.23.depot.gz

under /:

first install all dependencies,

gunzip libiconv-1.12-hppa-11.23.depot.gz
swinstall -s /libiconv-1.12-hppa-11.23.depot

In the window, select the package and then go to Actions --> Install. Do the same for all dependencies

Now, install bash

gunzip bash-3.2-hppa-11.23.depot.gz
swinstall -s /bash-3.2-hppa-11.23.depot

Once installed, appened to the path

find / -name bash

PATH=$PATH:/usr/local/bin
export PATH

that's all !!!!!!

How to install GRUB on MBR

2009-09-08T22:44:00.000-07:00

To install GRUB on MBR :

(First of all, enter your BIOS setup and in BOOT Sequence window choose to boot with CDROM first.)

1) Boot with your Fedora Core Installation CD 1 (or your Redhat Distro).

2) Type "linux rescue" at the prompt.

3) Answer the questions about keyboard and language.

4) Tell the rescue mode to use your proper partition to mount (the one that you want to get booted into)

5) When you come to the console prompt type: chroot /mnt/sysimage

6) Type grub

7) Set the GRUB's root device to the partition containing the boot directory like this:

grub> root (hd0,0)

Filesystem type is ext2fs, partition type 0x83

I have Windows 98 in hd0,0 ; Windows XP in hd0,1, Fedora Core /boot partition in hd0,2 and Mandrake /boot partition in hd0,6. So in my case the command should be: > root (hd0,2)

If you are not sure which partition actually holds this directory, use the command 'find' like this:

grub> find /boot/grub/stage1

This will search for the file name '/boot/grub/stage1' and show the devices which contain the file.
Once you've set the root device correctly, run the command 'setup'.

8) Then, run the command setup

grub> setup (hd0)
Checking if "/boot/grub/stage1" exists....... no
Checking if "/grub/stage1" exists....... yes
Checking if "/grub/stage2" exists....... yes
Checking if "/grub/e2fs_stage1_5" exists....... yes
Running "embed /grub/e2fs_stage1_5 (hd0)"....... 15 sectors are embedded
succeded
Running "install /grub/stage1 (hd0) (hd0) 1+15 p (hd0,2)/grub/stage2 /grub/grub.conf....... succeded
Done

This command will install GRUB boot loader on the Master Boot Record (MBR) of the first drive.

9) Type quit

grub> quit

GRUB is now in the MBR.

10) Finally, you'll have to edit your /boot/grub/grub.conf, for example whith nano:

> nano /boot/grub/grub.conf

(/etc/grub.conf or /boot/grub/grub.conf or /boot/grub/menu.lst, they are the same file) This file has the boot partitions of the disk/s.

11) Restart your PC without the Fedora Core CD 1 Installation. (or your Redhat Distro)
Reply With Quote

OR ALSO

you can also use this command

grub-install --recheck /dev/hda or /dev/sda.. it will correct the entries in grub.conf..

How to increase file descriptors max limit on Linux

2009-09-08T22:43:00.000-07:00

How to increase file descriptors max limit on Linux
===================================================

How do I increase the maximum number of open files under CentOS Linux? How do I open more file descriptors under Linux?

ulimit command provides control over the resources available to the shell and to processes started by it, on systems that allow such control. The maximum number of open file descriptors displayed with following command (login as the root)

cat /proc/sys/fs/file-max

output: 101703

The number of maximum files was reached, how do I fix this problem?

Increase file descriptor limit under Linux to prevent java.net.SocketException: Too many open files

Many application such as Oracle database server needs this range quite higher. So you can increase the maximum number of open files by setting new value in kernel variable /proc/sys/fs/file-max as follows (login as the root):

sysctl -w fs.file-max=200000

Above command forces the limit to 200000 files. You need to edit /etc/sysctl.conf file and put following line so that after reboot the setting will remain as it is:

vi /etc/sysctl.conf

and Append a config directive as follows:

fs.file-max = 200000

Save and close the file. Users need to log out and log back in again to changes take effect or just type command:

sysctl -p ( sysctl -p /etc/sysctl.conf)

Verify your settings with command:

cat /proc/sys/fs/file-max

or

sysctl fs.file-max

View how many files are open. The number returned might defer as 1 file descriptor can have multiple open files attached to it.

lsof | wc -l

Increase the limit:

Edit /etc/security/limits.conf

username hard nofile 32768

Detailed:

Max Processes per user limit , check this ulimit -a ( check the value next to max user processes )

max user processes (-u) 7168

To increase this value, go in to /root/.bashrc and type

ulimit -u unlimited

ou must exit and re-login from your terminal for the change to take effect.

check again, ulimit -a

max user processes unlimited

The above procedure will apply for all users since you edited root's bashrc file. If you want limit for a single user, then go in users bashrc file and change the limit as you want

You may also do ulimit -u unlimited at the command prompt instead of adding it to the /root/.bashrc file

II) Increases the system limit on open files for instance a process. Means, a process on a system can open at least 10000 file descriptors.

To see the number of open files per process, ulimit -a

open files (-n) 1024

To apply, go to /root/.bashrc and type

ulimit -n 5120

check the limit, ulimit -a

first I add the line
fs.file-max = 65536
into /etc/sysctl.conf and I reload with sysctl -p
then I add into /etc/security/limits the lines
* soft nofile 1024
* hard nofile 65535

third I add in /etc/pam.d/login the line

session required /lib/security/pam_limits.so

fourth I do

echo 65535 > /proc/sys/fs/file-max

HP-UX: Boot Into Single User Mode

2009-09-08T22:42:00.001-07:00

HP-UX: Boot Into Single User Mode

First, you need to interrupt the boot process when prompted. This is useful to reset password and other tasks.

First, you need to tell HP-UX box to boot primary, it should give you a prompt to interact with the ISL. You should reply 'y' to this. Once at ISL> prompt type hpux -is or hpux -iS /stand/vmunix to boot into single user mode

Interrupt the boot process when prompted by pressing [ESCAPE] key. You will see message as follows:

Selecting a system to boot. To stop selection process, press and hold the ESCAPE key...

OR

Autoboot from primary boot path enabled.
To override, press any key within 10 seconds

Type boot pri isl at the prompt:

boot pri

At the ISL> prompt:, type
hpux -is /stand/vmunix

or
hpux -is

or simply use, shutdown without any option will go to single user mode...

LINUX LVM :: How To...

2009-08-26T23:00:00.000-07:00

All these steps were tested on RHEL 5.3

Creating Physical Volumes:::

#fdisk /dev/sda
The number of cylinders for this disk is set to 4307.
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)

Command (m for help):p
Disk /dev/sda: 35.4 GB, 35433480192 bytes
255 heads, 63 sectors/track, 4307 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 16 128488+ 83 Linux
/dev/sda2 17 1928 15358140 8e Linux LVM
/dev/sda3 1929 2183 2048287+ 82 Linux swap / Solaris

I'm going to create a new partition about 5gb and use it as physical volume.

Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Selected partition 4
First cylinder (2184-4307, default 2184):
Using default value 2184
Last cylinder or +size or +sizeM or +sizeK (2184-4307, default 4307): +5g

Command (m for help): p

Disk /dev/sda: 35.4 GB, 35433480192 bytes
255 heads, 63 sectors/track, 4307 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 16 128488+ 83 Linux
/dev/sda2 17 1928 15358140 8e Linux LVM
/dev/sda3 1929 2183 2048287+ 82 Linux swap / Solaris
/dev/sda4 2184 2792 4891792+ 83 Linux

Command (m for help): t
Partition number (1-4): 4
Hex code (type L to list codes): 8e

Changed system type of partition 4 to 8e (Linux LVM)

Command (m for help): p

Disk /dev/sda: 35.4 GB, 35433480192 bytes
255 heads, 63 sectors/track, 4307 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 16 128488+ 83 Linux
/dev/sda2 17 1928 15358140 8e Linux LVM
/dev/sda3 1929 2183 2048287+ 82 Linux swap / Solaris
/dev/sda4 2184 2792 4891792+ 8e Linux LVM

Command (m for help): wq
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table.
The new table will be used at the next reboot.
Syncing disks.

#partprobe

To create a physical volume:::::::

[root@freedom ~]# pvcreate /dev/sda4
Physical volume "/dev/sda4" successfully created

[root@freedom ~]# pvs
PV VG Fmt Attr PSize PFree
/dev/sda2 vg00 lvm2 a- 14.62G 1.00G
/dev/sda4 lvm2 -- 4.67G 4.67G

[root@freedom ~]# pvdisplay -v
Scanning for physical volume names
Wiping cache of LVM-capable devices
--- Physical volume ---
PV Name /dev/sda2
VG Name vg00
PV Size 14.65 GB / not usable 22.18 MB
Allocatable yes
PE Size (KByte) 32768
Total PE 468
Free PE 32
Allocated PE 436
PV UUID lDu5U5-ExhK-CNGK-jcH7-Koj3-CIhc-vRWCZo

"/dev/sda4" is a new physical volume of "4.67 GB"
--- NEW Physical volume ---
PV Name /dev/sda4
VG Name
PV Size 4.67 GB
Allocatable NO
PE Size (KByte) 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID r4R03g-12qu-iRO5-56Fl-nCwa-mPoh-3zgy6n

To remove a physical volume use::::::

[root@freedom ~]# pvremove /dev/sda4
Labels on physical volume "/dev/sda4" successfully wiped
[root@freedom ~]# pvs
PV VG Fmt Attr PSize PFree
/dev/sda2 vg00 lvm2 a- 14.62G 1.00G
[root@freedom ~]# pvdisplay -v
Scanning for physical volume names
--- Physical volume ---
PV Name /dev/sda2
VG Name vg00
PV Size 14.65 GB / not usable 22.18 MB
Allocatable yes
PE Size (KByte) 32768
Total PE 468
Free PE 32
Allocated PE 436
PV UUID lDu5U5-ExhK-CNGK-jcH7-Koj3-CIhc-vRWCZo

we again create a same physical volume::::

[root@freedom ~]# pvcreate -f /dev/sda4
Physical volume "/dev/sda4" successfully created

let me create a couple more partition to make a physical volume

[root@freedom ~]# pvs
PV VG Fmt Attr PSize PFree
/dev/sda2 vg00 lvm2 a- 14.62G 1.00G
/dev/sda4 lvm2 -- 4.67G 4.67G

/dev/sda5 2184 2549 2939863+ 83 Linux
/dev/sda6 2550 2915 2939863+ 83 Linux
/dev/sda7 2916 3281 2939863+ 83 Linux

the above are new physical volumes of 3 gb each.... ignore the above physical volume

[root@freedom ~]# pvcreate /dev/sda5 /dev/sda6 /dev/sda7
Physical volume "/dev/sda5" successfully created
Physical volume "/dev/sda6" successfully created
Physical volume "/dev/sda7" successfully created
[root@freedom ~]#

lets create a volume group vg01 and two physical volumes to it (/dev/sda5,/dev/sda6)

[root@freedom ~]# vgcreate vg01 /dev/sda5 /dev/sda6
Volume group "vg01" successfully created

[root@freedom ~]# vgs
VG #PV #LV #SN Attr VSize VFree
vg00 1 6 0 wz--n- 14.62G 1.00G
vg01 2 0 0 wz--n- 5.60G 5.60G

on vg00 there is a free space about 1g left and on vg01 there is a free space left is 5g

Now we are going to create a logical volume under vg01 and mount it....

[root@freedom ~]# lvcreate -L 500M -n lvol_test /dev/vg01
Logical volume "lvol_test" created

500m of new logical volume lvol_test has been created...check that

[root@freedom ~]# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
lvol_home vg00 -wi-ao 1.94G
lvol_opt vg00 -wi-ao 992.00M
lvol_root vg00 -wi-ao 2.91G
lvol_tmp vg00 -wi-ao 1.97G
lvol_usr vg00 -wi-ao 3.91G
lvol_var vg00 -wi-ao 1.94G
lvol_test vg01 -wi-a- 500.00M

Now creating a file system on it....

[root@freedom ~]# mkfs.ext3 /dev/vg01/lvol_test
mke2fs 1.39 (29-May-2006)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
128016 inodes, 512000 blocks
25600 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67633152
63 block groups
8192 blocks per group, 8192 fragments per group
2032 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409

Writing inode tables: done
Creating journal (8192 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.

mount it,

[root@freedom ~]# mount -t ext3 /dev/vg01/lvol_test /test

[root@freedom ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg00-lvol_root
2.9G 337M 2.4G 13% /
/dev/mapper/vg00-lvol_home
1.9G 36M 1.8G 2% /home
/dev/mapper/vg00-lvol_tmp
2.0G 759M 1.1G 41% /tmp
/dev/mapper/vg00-lvol_var
1.9G 91M 1.7G 5% /var
/dev/mapper/vg00-lvol_opt
961M 18M 895M 2% /opt
/dev/mapper/vg00-lvol_usr
3.8G 2.1G 1.6G 58% /usr
/dev/sda1 122M 15M 101M 13% /boot
tmpfs 442M 0 442M 0% /dev/shm
/dev/mapper/vg01-lvol_test
485M 11M 449M 3% /test

we need to add this to /etc/fstab to make it permanent upon reboots

/dev/vg01/lvol_test /test ext3 defaults 1 2

we're now extending our file system since it is reached to its extend

/dev/mapper/vg01-lvol_test
485M 394M 66M 86% /test

[root@freedom ~]# lvextend -L +1G /dev/vg01/lvol_test

Extending logical volume lvol_test to 1.49 GB
Logical volume lvol_test successfully resized

[root@freedom ~]# resize2fs /dev/vg01/lvol_test

resize2fs 1.39 (29-May-2006)
Filesystem at /dev/vg01/lvol_test is mounted on /test; on-line resizing required
Performing an on-line resize of /dev/vg01/lvol_test to 1560576 (1k) blocks.
The filesystem on /dev/vg01/lvol_test is now 1560576 blocks long.

[root@freedom ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg00-lvol_root
2.9G 337M 2.4G 13% /
/dev/mapper/vg00-lvol_home
1.9G 36M 1.8G 2% /home
/dev/mapper/vg00-lvol_tmp
2.0G 759M 1.1G 41% /tmp
/dev/mapper/vg00-lvol_var
1.9G 91M 1.7G 5% /var
/dev/mapper/vg00-lvol_opt
961M 18M 895M 2% /opt
/dev/mapper/vg00-lvol_usr
3.8G 2.1G 1.6G 58% /usr
/dev/sda1 122M 15M 101M 13% /boot
tmpfs 442M 0 442M 0% /dev/shm
/dev/mapper/vg01-lvol_test
1.5G 394M 1007M 29% /test

kool, /test is now 1g free space..

Now we are extending vg00 volume group (adding a physical volume /dev/sda7 to it)

[root@freedom ~]# vgextend vg00 /dev/sda7
Volume group "vg00" successfully extended

vgdisplay -v vg00

--- Physical volumes ---
PV Name /dev/sda2
PV UUID lDu5U5-ExhK-CNGK-jcH7-Koj3-CIhc-vRWCZo
PV Status allocatable
Total PE / Free PE 468 / 32

PV Name /dev/sda7
PV UUID LKfPTr-Z4Ts-KFYi-FPHM-Y0Lk-MEQz-jAITG6
PV Status allocatable
Total PE / Free PE 89 / 89

Shrink an LVM::::::

we have a logical volume (/dev/vg-mirror/test) mounted on /test with 300MB size and we would like to reduce it by 100MB
it should be reduced to 200Mb from 300Mb (less 100m).. here are the steps

These are performed on rhel 5

first unmount /test logical volume

#umount /test

perform a check of file system

#e2fsck -f /dev/vg-mirror/test

resize the file system first

#resize2fs /dev/vg-mirror/test 200M

Then reduce the size of the logical volume

#lvreduce -L -100M /dev/vg-mirror/test

then mount it back on /test and check for data..

mount /dev/vg-mirror/test /test

it is strongly recommended to backup your data before performing above steps for safe side...

Mirroring::::::

we do normally mirror logical volumes not the disks. The same even applied to HP-UX LVM... To mirror, you need atleast
two disks (ex, /dev/sdd , /dev/sde). we create a large partition (or entire disk partition) on these two disks and use it as mirror for newly created
logical volumes

pvcreate /dev/sdd1 /dev/sde1

now create a volume group

vgcreate /dev/vg-mirror /dev/sdd1 /dev/sde1

then create a logical volume

lvcreate -L +1G -m1 -n mirror /dev/vg-mirror

this should be a mirror lvm... mount this and test your self (by adding some files and destroying one physical volume and check for the data)

Setting up Veritas Volumes on HP

2009-08-19T03:54:00.000-07:00

Setting up Veritas Volumes on HP

Once the LUNs have been presented to the host from the CX:

Step 1: Run ioscan and insf to build the hardware paths and load the device drivers for the new disks:

ioscan -fnC disk
insf -e

Step 2: Run the ioscan, insf and powermt commands to make the LUNs visible to the OS

powermt display
powermt check
powermt config
powermt save
powermt display
vxdctl enable

Step 3: Find a disk to add to the disk group

vxdisk list

DEVICE TYPE DISK GROUP STATUS
c2t0d0 simple rootdisk01 rootdg online
c2t1d0 simple rootmirr01 rootdg online
c4t3d0 simple - - error
c8t0d0 simple - - online invalid
c8t0d1 simple - - online invalid
c8t0d2 simple - - online invalid
c8t0d3 simple - - online invalid
c8t0d4 simple - - online invalid
c8t0d5 simple - - online invalid
c8t0d6 simple - - online invalid
c8t0d7 simple - - online invalid
c8t1d0 simple - - online invalid
c8t1d1 simple - - online invalid

vxdisksetup -i c8t0d0

Step 4: If a group is not set up for use, create a disk group:

vxdg init bedvqa03fs bedvqa03fs01=c8t0d0

If a group is set up for use, add the disk to the disk group:

vxdg -g bedvqa03fs adddisk bedvqa03fs02=c8t0d1

Step 5: confirm the work you just completed:

vxdg list
vxdg list bedvqa03fs
vxprint -g bedvqa03fs
vxdg -g bedvqa03fs free

Step 6: Create a raw volume in the disk group:

/usr/sbin/vxassist -g bedvqa03fs -U gen make sybsystemdb 64m layout=nolog user=sybase group=database mode=0755 bedvqa03fs01

This completes the work of setting up Veritas Volumes on HP.

Command line for volume manager

2009-08-19T03:51:00.000-07:00

Command line for volume manager.

Free space on the disk : vxdg free

Rename disk: vxedit –g (disk group name) rename disk_1 ( disk name ) test_1 ( disk name)

Remove disk: vxdg –g testdg ( dg name) rmdisk testdg_02 ( disk name )

Add disk: vxdg –g testdg ( dg name ) adddisk disk_1(disk name)=cxtxdx

Deport disk: vxdg –n rootdg deport testdg ( dg name).

Create disk group: vxdg init testdg ( dg name) disk_01( disk nam)=cxtxdx

Create volume: vxassist –g testdg ( dg name) –U fsgen make vol01 ( volume name)100m: option layout=(stripe,nolog) user=xxxx group=xxx mode=755 disk_01 disk_02 …. ( disk name )

Add mirror: vxassist –g testdg ( dg name ) mirror vol01 ( volume name) layout=(stripe,simple)

Remote log or mirror: vxedit –g testdg ( dg name) –r rm vol01-02 ( plex name)

Create subdisk: vxmake –g testdg (dg name) sd (subdisk name) dm_name=(disk name) dm_offset=0 ( start sector) len=204800 (sectors, 1 sector =512byte )

Create Plex: vxmake –g testdg ( dg name) plex pl-01 ( plex name) layout = STRIPE st_width=128 ncolume=3 ( number of subdisk join together) sd= disk_01, disk_02 ….( subdisk name)

Join plex become mirror: vxplex –g testdg ( dg name) att vol01 ( volume name) pl-01 ( plex name)

Enlarge volume: vxassist –g testdg ( dg name) growto vol_01 ( volume name ) 300m ( new size)

Stop and start volume: vxvol –g testdg ( dg name) start/ stop vol_01 ( volume name)

Dissociate the plex: vxplex –g tesetdg ( dg name) dis pl-01 ( plex name)

Remove volume: vxedit –g testdg ( dg name ) –rf rm vol_01 ( volume name) … ( -rf is the force option)

Add log: vxassist –g testdg ( dg name) addlog vol01 ( volume name) testdg_04 ( disk name)

Remove disk from VM: vxdisk rm c1t0d0

Remove disk from VM totally: vxdiskunsetup –c c1t0d0

To start vxconfigd: vxconfigd -m boot ( You have to wait for a while to complete its configuration file)

To upgrade disk group: vxdg upgrade testdg ( disk group name)

All other: vxdisk –s list, vxserial –p , vxiod, vxprint –ht, vxdctl , vxlicense

To create volume with plex: vxmake –U fsgen –g testdg vol ( volume name) read_pol=select user=root group=other mode=755 log_type=none len=2048000( sector) plex=pl-01 ( plex name)

Fix plex in stale mode: vxmend fix stale oradata_07-01 ( plex name, it should be brown at the time)

Fix plex in clean stage: vxmend fix clean oraddata_07-01 ( plex name, after that it can start the volume and mount file system)

Import the disk group by force: vxdg –f import qaswb ( disk group name )

Flush the disk group: vxdg flush qaswb ( disk group name, it safe to do that.)

Clean up volumes vxconfigd -k cleartempdir

Move and Resize Live Filesystems on a VxVM disk

2009-08-19T03:44:00.000-07:00

It is assumed that the new disks/LUNs are already installed in/presented to the host and initialised into VxVM.

1. Verify that there is enough space on the VxVM disk(s):

# vxdg -g diskgroup free disk-id
eg.:
root@freedom# vxdg -g filesystems free c1t3d0
DISK DEVICE TAG OFFSET LENGTH FLAGS
c1t3d0 c1t3d0s2 c1t3d0 65024640 6298944 -
c1t3d0 c1t3d0s2 c1t3d0 115365312 8385024 -
c1t3d0 c1t3d0s2 c1t3d0 134241792 9076992 -

2. If so, continue to step 4; otherwise verify that there is a disk with enough free space in the group:

# vxdg -g diskgroup free | nawk '($1 ~ /^c/) {print $1, $5/2048 "MB"}'
eg.:
root@freedom# vxdg -g filesystems free | nawk '($1 ~ /^c/) {print $1, $5/2048 "MB"}'
c1t2d0 61791.4MB
c1t3d0 3075.66MB
c1t3d0 4094.25MB
c1t3d0 4432.12MB
c1t4d0 3075.66MB
c1t4d0 4094.25MB
c1t4d0 4432.12MB
c1t5d0 61791.4MB

3. Then move the volume from the current disk:

# vxassist -g diskgroup move volume \!current disk
(do the same for any disk mirrors)
eg:
root@freedom# vxassist -g filesystems move oracle9 \!c1t3d0
root@freedom# vxassist -g filesystems move oracle9 \!c1t4d0
root@freedom# vxprint -htg filesystems | grep oracle9
v oracle9 - ENABLED ACTIVE 16777216 SELECT - fsgen
pl oracle9-01 oracle9 ENABLED ACTIVE 16780224 CONCAT - RW
sd c1t5d0-01 oracle9-01 c1t5d0 0 6298944 0 c1t5d0s2 ENA
sd c1t5d0-02 oracle9-01 c1t5d0 6298944 10481280 6298944 c1t5d0s2 ENA
pl oracle9-02 oracle9 ENABLED ACTIVE 16780224 CONCAT - RW
sd c1t2d0-01 oracle9-02 c1t2d0 0 6298944 0 c2t2d0 ENA
sd c1t2d0-02 oracle9-02 c1t2d0 6298944 10481280 6298944 c2t2d0 ENA

4. Finally, grow the filesystem with:

# vxresize -g diskgroup volume size
eg.:
root@freedom# vxresize -g filesystems oracle9 8192m
root@freedom# df -k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d100 4637056 1889665 2701021 42% /
/dev/md/dsk/d150 12096820 3130130 8845722 27% /usr
/proc 0 0 0 0% /proc
mnttab 0 0 0 0% /etc/mnttab
fd 0 0 0 0% /dev/fd
/dev/md/dsk/d160 1984564 936477 988551 49% /var
swap 10103888 24 10103864 1% /var/run
dmpfs 10103864 0 10103864 0% /dev/vx/dmp
dmpfs 10103864 0 10103864 0% /dev/vx/rdmp
swap 10103976 112 10103864 1% /tmp
/dev/vx/dsk/filesystems/srcat
20643785 13994542 6442806 69% /srcat
/dev/vx/dsk/filesystems/oracle
7224765 3805306 3347212 54% /oracle
/dev/vx/dsk/filesystems/netbackup
25804343 19320452 6225848 76% /usr/openv
/dev/vx/dsk/filesystems/patrol01
4915164 1653364 2770284 38% /opt/patrol
/dev/md/dsk/d170 12096820 8397540 3578312 71% /export/home
/dev/vx/dsk/filesystems/oracle9
7864272 4924788 2251361 69% /apps/oracle

Solaris- Steps to gain root access without the root password

2009-08-19T03:38:00.001-07:00

Step 1: Place the installation CD into the server and interrupt the boot sequence.

Step 2: At the {OK} prompt boot to single user mode from the CD.

{OK} boot cdrom –s

Step 3: Once the server boots into single user mode, identify the root disk:

# format
Searching for disks…done

AVAILABLE DISK SELECTIONS:
0. c0t0d0
/pci@1f,0.ide@d/dad@0,0
1. c0t2d0
/pci@1f,0/ide@d/dad@2,0
Speecify disk (enter its number):

Step 4: Mount the root (/) file system to /mnt

# mount /dev/dsk/c0t0d0s0 /mnt

Step 4: Edit the shadow file:

# vi /mnt/etc/shadow

root:rAAeloFlBGHwc:6445::::::
daemon:NP:6445::::::
bin:NP:6445::::::
sys:NP:6445::::::
adm:NP:6445::::::
lp:NP:6445::::::
uucp:NP:6445::::::
nuucp:NP:6445::::::
smmsp:NP:6445::::::
listen:*LK*:6445::::::
gdm:*LK*:6445::::::
webservd:*LK*:6445::::::
nobody:*LK*:6445::::::
noaccess:*LK*:6445::::::
nobody4:*LK*:6445::::::

Change the root password entry to look like the following:

root::6445::::::

Step 5: Save your changes and reboot the server as you normally would.

# reboot

Step 6: Log on as root and change the root password:

# passwd root

These actions were performed on a Sun workstation, but the general procedure remains the same for most UNIX varieties.

Setting up a NIS Server on LINUX (RHEL 5.3)

2009-08-16T00:58:00.000-07:00

Network Information Services (NIS) enables you to create user accounts that can be shared across all systems on your network. The user account is created only on the NIS server. NIS clients download the necessary username and password data from the NIS server to verify each user login.

This example we use NIS server, NFS server (to mount home directories) and NIS client.

1. Configure freedom as an NFS server to make its /home directory available to the Linux workstations.
2. Configure wisdom as an NFS client that can access freedom's /home directory.
3. Configure freedom as an NIS server.
4. Create a user account (nisuser) on freedom that doesn't exist on wisdom. Convert the account to a NIS user account.
5. Configure wisdom as an NIS client.
6. Test a remote login from freedom to wisdom using the username and password of the account nisuser.

In a Nutshell, freedom is configured as NIS and NFS server and wisdom is configured as NIS and NFS client. Both are LINUX boxes with RHEL 5.3 installed on it.

First I am configuring a NIS server on freedom:::

Packages:
ypserv-2.19-5.el5
yp-tools-2.9-0.1
ypbind-1.19-11.el5

Edit Your /etc/sysconfig/network File
#/etc/sysconfig/network
NISDOMAIN="free.com"

Edit Your /etc/yp.conf File
# /etc/yp.conf - ypbind configuration file
ypserver 127.0.0.1

Start The Key NIS Server Related Daemons
service portmap start
service yppasswdd start
service ypserv start

chkconfig portmap on
chkconfig yppasswdd on
chkconfig ypserv on

Make sure they are all running before continuing to the next step. You can use the rpcinfo command to do this.

[root@freedom ~]# rpcinfo -p localhost
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100004 2 udp 660 ypserv
100004 1 udp 660 ypserv
100004 2 tcp 663 ypserv
100004 1 tcp 663 ypserv
100007 2 udp 876 ypbind
100007 1 udp 876 ypbind
100007 2 tcp 879 ypbind
100007 1 tcp 879 ypbind
600100069 1 udp 905 fypxfrd
600100069 1 tcp 907 fypxfrd
100011 1 udp 752 rquotad
100011 2 udp 752 rquotad
100011 1 tcp 755 rquotad
100011 2 tcp 755 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100021 1 udp 41493 nlockmgr
100021 3 udp 41493 nlockmgr
100021 4 udp 41493 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100021 1 tcp 48865 nlockmgr
100021 3 tcp 48865 nlockmgr
100021 4 tcp 48865 nlockmgr
100005 1 udp 766 mountd
100005 1 tcp 769 mountd
100005 2 udp 766 mountd
100005 2 tcp 769 mountd
100005 3 udp 766 mountd
100005 3 tcp 769 mountd
100024 1 udp 823 status
100024 1 tcp 826 status
100009 1 udp 867 yppasswdd

The ypbind and ypxfrd daemons won't start properly until after you initialize the NIS domain. You'll start these daemons after initialization is completed.

Initialize Your NIS Domain

[root@freedom ~]#/usr/lib/yp/ypinit -m
At this point, we have to construct a list of the hosts which will run NIS
servers. freedom is in the list of NIS server hosts. Please continue to add
the names for the other hosts, one per line. When you are done with the
list, type a .
next host to add: freedom
next host to add:
The current list of NIS servers looks like this:

freedom

Is this correct? [y/n: y] y
We need a few minutes to build the databases...
Building .........
...

freedom has been set up as a NIS master server.

Now you can run ypinit -s freedom on all slave server.

Start The ypbind and ypxfrd Daemons

# service ypbind start
# service ypxfrd start

# chkconfig ypbind on
# chkconfig ypxfrd on

Make Sure The Daemons Are Running
[root@freedom ~]# rpcinfo -p localhost

Adding New NIS Users:

#useradd nisuser
#passwd nisuser

#cd /var/yp
#make

whenever you add a new user, please make sure to go to /var/yp and run "make" command

You can check to see if the user's authentication information has been updated by using the ypmatch command, which should return the user's encrypted password string.

[root@freedom ~]# ypmatch nisuser passwd
nisuser:$1$0TeJhdDy$HY.DWfJGdTEphrcJB5XAP/:507:507::/home/nisuser:/bin/bash

[root@freedom ~]# getent passwd nisuser
nisuser:x:507:507::/home/nisuser:/bin/bash

Configuration of NIS server is completed!!

Configuring The NIS Client

Run authconfig

The authconfig or the authconfig-tui program automatically configures your NIS files after prompting you for the IP address and domain of the NIS server.

#authconfig-tui

Once finished, it should create an /etc/yp.conf file that defines, amongst other things, the IP address of the NIS server for a particular domain. It also edits the /etc/sysconfig/network file to define the NIS domain to which the NIS client belongs.

# /etc/yp.conf - ypbind configuration file
domain free.com server 192.168.1.3

#/etc/sysconfig/network
NISDOMAIN=free.com

In addition, the authconfig program updates the /etc/nsswitch.conf file that lists the order in which certain data sources should be searched for name lookups, such as those in DNS, LDAP, and NIS. Here you can see where NIS entries were added for the important login files.

#/etc/nsswitch.conf
passwd: files nis
shadow: files nis
group: files nis

Start The NIS Client Related Daemons

# service portmap start
# service ypbind start
# chkconfig ypbind on
# chkconfig portmap on

Note: Remember to use the rpcinfo -p localhost command to make sure they all started correctly.

Test NIS Access To The NIS Server

You can run the ypcat, ypmatch, and getent commands to make sure communication to the server is correct.

[root@wisdom ~]# ypcat passwd
nisuser:$1$0TeJhdDy$HY.DWfJGdTEphrcJB5XAP/:507:507::/home/nisuser:/bin/bash
nis2:$1$94fzrnHN$DI16sL.ch51EbRPxujigI/:508:508::/home/nis2:/bin/bash

[root@wisdom ~]# ypmatch nisuser passwd
nisuser:$1$0TeJhdDy$HY.DWfJGdTEphrcJB5XAP/:507:507::/home/nisuser:/bin/bash

[root@wisdom ~]# getent passwd nisuser
nisuser:$1$0TeJhdDy$HY.DWfJGdTEphrcJB5XAP/:507:507::/home/nisuser:/bin/bash

It looks all is well.

NIS client configuration is completed!!

We can now try connecting to wisdom server using nisuser/passwd that was set up on NIS server. The output is, we will be able to connect to the server fine and authentication was successful. But the problem is home directory, it tries to load the home directory from the local computer (wisdom) and gives an error.
chroot unable to mount the /home directory..

To fix this we need to set up a NFS server to mount all our nisuser home directories automatically (using automounter)

Configuring The NFS Server

1. Edit the /etc/exports file to allow NFS mounts of the /home directory with read/write access.

/home *(rw,sync)

# exportfs -ra

# chkconfig nfslock on
# chkconfig nfs on
# chkconfig portmap on
# service portmap start
# service nfslock start
# service nfs start

[root@freedom ~]# showmount -e localhost
Export list for localhost:
/home *
/test 192.168.1.4

Configuring The NFS Client:

1. Make sure the required netfs, nfslock, and portmap daemons are running and configured to start after the next reboot.

# chkconfig nfslock on
# chkconfig netfs on
# chkconfig portmap on
# service portmap start
# service netfs start
# service nfslock start

2. Keep a copy of the old /home directory, and create a new directory /home on which you'll mount the NFS server's directory.

# mv /home /home.old
# mkdir /home

3. Make sure you can mount freedom's /home directory on the new /home directory you just created. Unmount it once everything looks correct.

# mount 192.168.1.3:/home /home/

# umount /home

4. Start configuring autofs automounting. Edit your /etc/auto.master file to refer to file /etc/auto.misc for mounting information whenever the /home directory is accessed. After five minutes, autofs unmounts the directory.

#/etc/auto.master
/home /etc/auto.misc --timeout 600

5. Edit file /etc/auto.misc to do the NFS mount whenever the /home directory is accessed.

* -fstype=nfs,soft,intr,rsize=8192,wsize=8192,nosuid,tcp 192.168.1.3:/home/&

Start autofs and make sure it starts after the next reboot with the chkconfig command.

#chkconfig autofs on
#service autofs restart

Now the NIS user was able to login and mount the home directoy..

How to find the WWN (World Wide Name) in Sun Solaris

2009-07-24T04:10:00.000-07:00

World Wide Name (WWN) are unique 8 byte (64-bit) identifiers in SCSI or fibre channel similar to that of MAC Addresses on a Network Interface Card (NIC).

Talking about the WWN names, there are also

World Wide port Name (WWpN), a WWN assigned to a port on a Fabric which is what you would be looking for most of the time.

World Wide node Name (WWnN), a WWN assigned to a node/device on a Fibre Channel fabric.

To find the WWN numbers of your HBA card in Sun Solaris, you can use one the following procedures

Using fcinfo (Solaris 10 only)

This is probably the easiest way to find the WWN numbers on your HBA card. Here you can see the HBA Port WWN (WWpN) and the Node WWN (WWnN) of the two ports on the installed Qlogic HAB card.

This is also useful in finding the Model number, Firmwar version FCode, supported and current speeds and the port status of the HBA card/port

root@ sunserver:/root# fcinfo hba-port | grep WWN
HBA Port WWN: 2100001b32xxxxxx
Node WWN: 2000001b32xxxxxx
HBA Port WWN: 2101001b32yyyyyy
Node WWN: 2001001b32yyyyyy

Using scli:

bash-3.00# /opt/QLogic_Corporation/SANsurferCLI/scli -i | egrep "Node Name|Port Name"
Error: Cannot open/read the menu configuration file - /etc/menu.properties!
Node Name : 20-00-00-E0-8B-8A-5D-1E
Port Name : 21-00-00-E0-8B-8A-5D-1E
Node Name : 20-00-00-E0-8B-19-2B-A0
Port Name : 21-00-00-E0-8B-19-2B-A0

Using prtconf:

bash-3.00# prtconf -vp | grep -i wwn
adapter-wwn: 210000e0.8b8a5d1e
adapter-wwn: 210000e0.8b192ba0

Using prtpicl:

bash-3.00# prtpicl -v | grep wwn
:adapter-wwn 21 00 00 e0 8b 8a 5d 1e
:adapter-wwn 21 00 00 e0 8b 19 2b a0

How to find the WWN (World Wide Name) in Sun Solaris
February 10, 2009 · Filed Under hardware

World Wide Name (WWN) are unique 8 byte (64-bit) identifiers in SCSI or fibre channel similar to that of MAC Addresses on a Network Interface Card (NIC).

Talking about the WWN names, there are also

World Wide port Name (WWpN), a WWN assigned to a port on a Fabric which is what you would be looking for most of the time.

World Wide node Name (WWnN), a WWN assigned to a node/device on a Fibre Channel fabric.

To find the WWN numbers of your HBA card in Sun Solaris, you can use one the following procedures

Using fcinfo (Solaris 10 only)

This is probably the easiest way to find the WWN numbers on your HBA card. Here you can see the HBA Port WWN (WWpN) and the Node WWN (WWnN) of the two ports on the installed Qlogic HAB card.

This is also useful in finding the Model number, Firmwar version FCode, supported and current speeds and the port status of the HBA card/port.

root@ sunserver:/root# fcinfo hba-port | grep WWN
HBA Port WWN: 2100001b32xxxxxx
Node WWN: 2000001b32xxxxxx
HBA Port WWN: 2101001b32yyyyyy
Node WWN: 2001001b32yyyyyy

For detailed info including Make & model number, Firmware, Fcode and current status and supported/current speeds then

root@ sunserver:/root# fcinfo hba-port
HBA Port WWN: 2100001b32xxxxxx
OS Device Name: /dev/cfg/c2
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 4.04.01
FCode/BIOS Version: BIOS: 1.24; fcode: 1.24; EFI: 1.8;
Type: N-port
State: online
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: 4Gb
Node WWN: 2000001b32xxxxxx
HBA Port WWN: 2101001b32yyyyyy
OS Device Name: /dev/cfg/c3
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 4.04.01
FCode/BIOS Version: BIOS: 1.24; fcode: 1.24; EFI: 1.8;
Type: unknown
State: offline
Supported Speeds: 1Gb 2Gb 4Gb
Current Speed: not established
Node WWN: 2001001b32yyyyyy

Using scli

root@ sunserver:/root# scli -i | egrep “Node Name|Port Name”
Node Name : 20-00-00-1B-32-XX-XX-XX
Port Name : 21-00-00-1B-32-XX-XX-XX
Node Name : 20-01-00-1B-32-YY-YY-YY
Port Name : 21-01-00-1B-32-YY-YY-YY

For more detailed info on the HBA Cards run as follows: Similar to fcinfo but also provides Model Name and serial number.

root@ sunserver:/root# scli -i
——————————————————————————
Host Name : sunserver
HBA Model : QLE2462
HBA Alias :
Port : 1
Port Alias :
Node Name : 20-00-00-1B-32-XX-XX-XX
Port Name : 21-00-00-1B-32-XX-XX-XX
Port ID : 11-22-33
Serial Number : AAAAAAA-bbbbbbbbbb
Driver Version : qlc-20080514-2.28
FCode Version : 1.24
Firmware Version : 4.04.01
HBA Instance : 2
OS Instance : 2
HBA ID : 2-QLE2462
OptionROM BIOS Version : 1.24
OptionROM FCode Version : 1.24
OptionROM EFI Version : 1.08
OptionROM Firmware Version : 4.00.26
Actual Connection Mode : Point to Point
Actual Data Rate : 2 Gbps
PortType (Topology) : NPort
Total Number of Devices : 2
HBA Status : Online
——————————————————————————
Host Name : sunserver
HBA Model : QLE2462
HBA Alias :
Port : 2
Port Alias :
Node Name : 20-01-00-1B-32-YY-YY-YY
Port Name : 21-01-00-1B-32-YY-YY-YY
Port ID : 00-00-00
Serial Number : AAAAAAA-bbbbbbbbbb
Driver Version : qlc-20080514-2.28
FCode Version : 1.24
Firmware Version : 4.04.01
HBA Instance : 3
OS Instance : 3
HBA ID : 3-QLE2462
OptionROM BIOS Version : 1.24
OptionROM FCode Version : 1.24
OptionROM EFI Version : 1.08
OptionROM Firmware Version : 4.00.26
Actual Connection Mode : Unknown
Actual Data Rate : Unknown
PortType (Topology) : Unidentified
Total Number of Devices : 0
HBA Status : Loop down

Using prtconf

root@ sunserver:/root# prtconf -vp | grep -i wwn
port-wwn: 2100001b.32xxxxxx
node-wwn: 2000001b.32xxxxxx
port-wwn: 2101001b.32yyyyyy
node-wwn: 2001001b.32yyyyyy

Using prtpicl

root@ sunserver:/root# prtpicl -v | grep wwn
:node-wwn 20 00 00 1b 32 xx xx xx
:port-wwn 21 00 00 1b 32 xx xx xx
:node-wwn 20 01 00 1b 32 yy yy yy
:port-wwn 21 01 00 1b 32 yy yy yy

Using luxadm:

Run the following command to obtain the physical path to the HBA Ports

root@ sunserver:/root$ luxadm -e port
/devices/pci@400/pci@0/pci@9/SUNW,qlc@0/fp@0,0:devctl CONNECTED
/devices/pci@400/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0:devctl NOT CONNECTED

With the physical path obtained from the above command, we can trace the WWN numbers as follows. here I use the physical path to the one that is connected:

root@ sunserver:/root$ luxadm -e dump_map /devices/pci@400/pci@0/pci@9/SUNW,qlc@0/fp@0,0:devctl
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 123456 0 1111111111111111 2222222222222222 0×0 (Disk device)
1 789123 0 1111111111111111 2222222222222222 0×0 (Disk device)
2 453789 0 2100001b32xxxxxx 2000001b32xxxxxx 0×1f (Unknown Type,Host Bus Adapter)

NFS server set up on Solaris 10

2009-07-24T02:48:00.000-07:00

NFS server set up (Quick Steps):

vi /etc/dfs/dfshare

share -F nfs -o rw /temp-bkup

svcadm enable nfs/server

ps -ef | grep nfs

share ( to see what has been shared)

Go to client machine and mount that nfs share

mkdir /temp-bkup

mount -F nfs -o rw rtb3:/temp-bkup /temp-bkup

or

mount -F nfs -o rw,hard,bg,proto=tcp,suid,rsize=32768,wsize=32768,intr,noac rtb3:/temp-bkup /temp-bkup

Add a LUN from CX to a Solaris Server

2009-07-09T04:02:00.000-07:00

Open Navisphere Global and login (using login credentials)

choose the Clariion connected to your host
open the storage groups tab and locate the group with your host attached to it.
Right click on the storage group and select “select luns”

A window will appear and all available drives are listed on the left.

choose the number of luns and move them to the right of the window, click ok

On the Solaris System

Verify the /kernel/drv/sd.conf has enough entries to handle the additional luns

Example, if there are 100 disk entries in the sd.conf file and you are adding a 101th LUN, you will need to make the following entry in the sd.conf file:

i. name="sd" class="scsi" target=48 lun=101 (assumes target is already set to 48)

run update_drv -f sd to import the luns into solaris
run devfsadm -Cv
run powercf –q
run powermt config
verify newly added luns are visible via format

In-Detail::::

run /usr/sbin/update_drv –f sd (this auto updates Solaris with the new lun)
run /usr/sbin/devfsadm -Cv (this auto updates Solaris with the devices)
run powermt display (retrieve listing of total # of devices)

OUTPUT:

root@sol-test # powermt display

Symmetrix logical device count=0

CLARiiON logical device count=474

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

----- Host Bus Adapters --------- ------ I/O Paths ----- ------ Stats ------

### HW Path Summary Total Dead IO/Sec Q-IOs Errors

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

1280 pci@8/fibre-channel@2 optimal 510 0 - 0 0

1281 pci@8/fibre-channel@3 optimal 438 0 - 0 0

1282 pci@9/fibre-channel@3 optimal 510 0 - 0 0

1283 pci@9/fibre-channel@4 optimal 438 0 - 0 0

run powercf –q
run powermt config
run powermt display (the # of disks should have increased)

OUTPUT:

Symmetrix logical device count=0

CLARiiON logical device count=474

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

----- Host Bus Adapters --------- ------ I/O Paths ----- ------ Stats ------

### HW Path Summary Total Dead IO/Sec Q-IOs Errors

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

1280 pci@8/fibre-channel@2 optimal 512 0 - 0 0

1281 pci@8/fibre-channel@3 optimal 438 0 - 0 0

1282 pci@9/fibre-channel@3 optimal 512 0 - 0 0

1283 pci@9/fibre-channel@4 optimal 438 0 - 0 0

Verify output by running the format command on solaris and label all the new disks.
Bring it into veritas by running vxdctl enable.
View the new disk using

· vxdisk list

Format the new disk and label it

format c2t16d11

Set up the new disk using

vxdisksetup -i c2t16d11 format=sliced

Add the newdisk to a disk group using

vxdg init dg01 disk01=c2t16d10s2 cds=off

Create a new file system using

/usr/sbin/vxassist -g dg01 -U fsgen make testfs 32g layout=nolog user=oracle group=dba mode=0755 disk01

Create a mount point for the new file system

mkdir /testdata

Place a new file system on the device

newfs -v /dev/vx/rdsk/dg01/testfs

Mount the file system

mount /dev/vx/dsk/dg01/testfs /testdata

Compile and Installation of GCC compiler (version: gcc-3.2.3)

2009-07-09T03:35:00.000-07:00

Host: RedHat Linux 4 ES up 4 (already gcc-3.4.6 installed on this machine).

Our DEV requires an older version of gcc (gcc-3.2.3) compiler installed on this machine to work. So I downloaded the older version from,

http://gcc.gnu.org/releases.html

Here are the steps I did,

# tar -xvf gcc-3.2.3.tar

# cd gcc-3.2.3

# ./configure --prefix=/opt/gcc-3.2.3 --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-java-awt=gtk --host=i386-redhat-linux

This is going to be installed under /opt/gcc-3.2.3 directory.

# make bootstrap

This is gonna be taking long time. Once its finished, run make install

# make install

This will end the installation. But there are couple of other things you need to take care of.

Post Installation Steps::::

There are a few tasks that you need to carry out after the installation process of the compilers.

Setting up PATH variable:::

export PATH=/opt/gcc-3.2.3/bin:$PATH

Add the above variable to /etc/profile

Setting the location of libraries::::

cat /etc/ld.so.conf (add the following line to it)

/opt/gcc-3.2.3/lib (this new line added to the existing file)
/usr/ofed/lib
/opt/OC/lib
/opt/nms/lib
/opt/nms/lib
/usr/lib/Pegasus/providers/
/usr/lib/

After editing this file, execute the ldconfig program, which will configure dynamic linker binding

# ldconfig -v

The next step is to setup the LD_LIBRARY_PATH variable. You can do this by adding the following line at the end of /etc/profile file so that it is set for all users at login time.

export LD_LIBRARY_PATH=/opt/gcc-3.2.3/lib

Finally, check the version and compilation options,

#gcc -v
[root@pearl sasam]# gcc -v
Reading specs from /opt/gcc-3.2.3/lib/gcc-lib/i386-redhat-linux/3.2.3/specs
Configured with: ./configure --prefix=/opt/gcc-3.2.3 --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-java-awt=gtk --host=i386-redhat-linux
Thread model: posix
gcc version 3.2.3

HP-UX LVM

2009-07-02T02:51:00.001-07:00

The Logical Volume Manager (LVM) overcomes the limitations of the whole disk layout scheme by making
it possible to
• Create logical volumes that span multiple disks
• Create multiple logical volumes on a single disk
• Extend and reduce logical volumes as necessary

Physical Volumes ::::

A disk managed by LVM is known as a physical volume. Several special data structures must
be created on a disk before it can be used by LVM. Once these data structures have been
created, the disk is considered to be a physical volume, and may be added to a volume group

Volume Groups:::::

A volume group is group of one or more physical volumes.physical volumes in a volume group pool a disk space
which may be allocated to one or more logical volumes. Volume groups have the naming convention as,

/dev/vg00
/dev/vg01
/dev/vg02

Logical Volumes:

Disk space from volume group may be allocated to one or more logical volumes. A logical volume is equals to a partition
which may contain a file system , swap , raw data etc

-> then can span multiple LVM physical volumes
-> resized, extended or even moved to a different disk if needed

Naming convention for a logical volumes are,

/dev/vg00/lvol1
/dev/vg00/lvol2
/dev/vg01/lvol5

LVM device files ::::

Physical volumes, volume groups, and logical volumes are all referenced via device files, much
as disk devices are referenced via device files

/dev/dsk -> block pv device files
eg:
/dev/dsk/c0t5d0
/dev/dsk/c0t6d0

/dev/rdsk -> character raw pv device files
eg:
/dev/rdsk/c0t5d0
/dev/rdsk/c0t6d0

/dev/vg00 -> volume group device files
/dev/vg00/group -> volgume group vg00 device file
/dev/vg00/lvol1 -> lvol1 logical volume device file (block lv device file)
/dev/vg00/rlvol1 -> raw lv device file

/dev/vg00/lvol2 -> block lv (lvol2) device file
/dev/vg00/rlvol2 -> raw lv (lvol2) device file

physical volumes, volume groups and logical volumes are referenced via device files much like devices for accessing devices (like disk and tape)

Physical Volumes Device files:

You can refernece the physical volume using the device file associated with that physical volume. Since disk has referenced using block and raw mode, each physical volumes has both mode device files,

/dev/dsk/c0t5d0 # block device file for disk at SCSI address 5
/dev/rdsk/c0t5d0 # character device file for disk at SCSI address 5

Volume group device files::::

volume groups are referenced using device files. The volume group device files are stored under /dev containg group for device files for volume group vg00 and also device files for all logical volumes present under this volume group

ex:
/dev/vg00 # you can find all volume group and physical volumes device files here
/dev/vg00/group # referenced the device file for volume group vg00

Logical Volume Device files ::::

Logical volume device files are stored in the directory of the volume group to which they
belong. Each logical volume has two device files: one is used when accessing the logical volume
in character mode, the other is used when accessing the logical volume in block mode

/dev/vg00/lvol1 #block device file for logical volume "lvol1" in vg00
/dev/vg00/rlvol1 #raw or character device file for logical volume "lvol1" in vg00

LVM major and minor numbers :::

unlike other deice files, the logical volumes and volume group device files has major and monior numbers. The major number for all logical volumes are same (it is 64)

the first two digits on the minor number represents the volgume group to which they(device file) belogs to.and the last two digits represents the logical volume number

eg, /dev/vg00/lvol2

major: 64

minoir: 0x000002

here, 00 after 0x represents the volume group vg00 in which this logical volume is created.
and 02 is logical volume number which is lvol02

Questions
If vg02 has three logical volumes created using the default naming convention

1. What directory would contain the logical volumes’ device files?
ans: /dev/vg02/
/dev/vg02/

2. What would be the name of the volume group’s device file?
ans:/dev/vg02/lvol1
/dev/vg02/rvol1

3. What would be the name of the first logical volume’s raw device file?

/dev/vg02/rvol1

4. Overall, how many device files should you find in /dev/vg02?
ans: 6 (3 for block and 3 for raw)

5. What would be the minor number of the third logical volume’s device file?
the third volume device file is,
/dev/vg02/lvol3

major: 64
minor:0x02003

LVM extends:::

QQQQQQQQQQQQQQQQQQQQQQQ
what is physical extent
what is logical extent.

The smallest allocatable unit of space in LVM is known as an "Extent."

A physical volume is broken into "Physical Extents" (PEs), which are made available for allocation when the
physical volume is added to a volume group.

A logical volume consists of a series of sequentially numbered "Logical Extents" (LEs). Each
logical extent is nothing more than a pointer to a physical extent on disk. Larger logical
volumes have more logical extents, and smaller logical volumes have fewer logical extents. In
order to make a logical volume larger, LVM needs only allocate some additional extents

Creating Physical Volumes:::

######################## things need to perform #################3333

• Create logical volumes that span multiple disks
• Create multiple logical volumes on a single disk
• Extend and reduce logical volumes as necessary

There are two disks present on the system (c0t3d0 and c0t4d0)

#pvcreate /dev/rdsk/c0t3d0 (why /dev/rdsk why not /dev/dsk)
#pvcreate /dev/rdsk/c0t4d0

execute the pvcreate command to create the LVM data structures needed by LVM to
begin using the disk as a physical volume.

If the disk was previously part of another volume group, you may need to use the -f option on pvcreate. To overwrite any existing LVM or file system structures on the disk.

# pvcreate -f /dev/rdsk/c0t3d0
# pvcreate -f /dev/rdsk/c0t4d0

Warning: The -f option should only be used as a last resort to over write file system or volume manager information that cannot properly be removed using the commands designed for that purpose. When invoked with -f, the command does minimal verification, so care should be taken to assure that the disk is not already in use prior to invoking the command.

Your disk is now ready to be added to a new or existing volume group.

LVM stores information in data structures at the beginning of the Physical Volume.

Physical Volume Reserved Area (PVRA) contains LVM information specific to that Physical Volume. It is created by the pvcreate command

Volume Group Reserved Area (VGRA): contains LVM information specific to the entire volume group

The VGRA is created by vgcreate command.

Bad Block Relocation Area (BBRA), contains information specific to the bad block
recovery mechanism

Creating Volume groups:::

commands:
mkdir /dev/vg01
mknod /dev/vg01/group c 64 0x010000
vgcreate vg01 /dev/rdsk/c0t3d0 /dev/rdsk/c0t4d0

check:
vgdisplay -v vg01
pvdisplay -v /dev/dsk/c0t3d0
pvdisplay -v /dev/dsk/c0t4d0

(while creating logical volumes, we take /dev/dsk block device rather than /dev/rdsk for setting up physical volumes at first place)

detailed:

Step 1:

Create a directory for the volume group. The naming convention is /dev/vgnn, where nn is
the volume group number. Use the next number in sequence on your system. If your system is
pre-installed, you already have a volume group /dev/vg00.

For example, to create volume group 01, which would be the second volume group on your
system, you would type:

mkdir /dev/vg01

Step 2:

The group special file, or control file, provides the means by which LVM kernel and LVM
commands communicate within the volume group you create

Create the control file named group in the directory /dev/vgnn. Use the mknod(1M)
command. The group file is a character device file. The major number is always 64. The minor
number is hexadecimal, always ends in 0000, and has the following form

0xhh0000
where hh is the hexadecimal representation of the volume group number.

For example, to create a group file for a volume group 01, you would type:

mknod /dev/vg01/group c 64 0x010000

Step3:

Now you can create the volume group and specify the physical volumes it will contain. You use
the vgcreate command. You can assign several volumes to a group at one time

vgcreate /dev/vg01 /dev/dsk/c0t3d0 /dev/dsk/c0t4d0

******** Note that you are using the block device file to create the volume group ********

vgcreate options are:::

-e max_physical_extents - sets the max number of physical extents per physical volume in a vg (1016 default)

-l max_logical_vols - sets the max number of logical volumes allowed in vg (255 default)

-p max_physical_vols - set the max number of LVM disks (physical volumes) should be allowed in vg (16)

-s physical_extent_size - sets the size in mb, for each physical extent in a volume group( 4mb default)

Step 4:

You can verify that you have created the volume group using the vgdisplay and pvdisplay
commands

# vgdisplay -v vg01

# pvdisplay /dev/dsk/c0t3d0

# pvdisplay /dev/dsk/c0t4d0

Creating logical Volumes:::

commands:

lvcreate -L 16 -n myfs1 vg01

lvcreate -L 20 -n myfs2 vg01

check: vgdisplay -v vg01

pvdisplay -v /dev/vg01/myfs1

Create logical volumes in volume groups using the lvcreate(1M) command

You can allocate disk space for file systems, swap, or raw data in either megabytes or LVM
extents

When lvcreate creates the logical volume, it creates the block and character device files and
places them in the directory /dev/vgnn. It is created without size unless you specify a size
when you use the lvcreate command. You can create a logical volume using the default
characteristics, and change them later

-L logical_volume_size - The size of the logical volume in MB.

-n name - The name of the logical volume

-l logical_extents_number - The number of logical extents in the logical volume.

examples:

To create a logical volume with the default characteristics, in the volume group /dev/vg01:

# lvcreate /dev/vg01

Only the name will be reserved; neither physical nor logical extents will be reserved. You will
need later to extend the logical volume with the command lvextend

To create a logical volume of 10 logical extents in size

lvcreate -l 10 /dev/vg01

To create a logical volume with a size of 100 Mbyte: (standared name is lvol3, lvol4 etc)

lvcreate -L 100 /dev/vg01

To create a logical volume with a non-standard name

lvcreate -L 100 -n myfs1 /dev/vg01

Viewing Your Logical Volumes::::

lvdisplay -v /dev/vg01/myfs1 # view details about the "myswap" LV

vgdisplay -v vg01 # to determine which LV’s are in vg01

Practicals ::::

Q.How many disks do you have on your system? Determine each disk’s hardware path and
device file names

Ans: bash-3.2# ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
============================================================================
disk 0 0/0/3/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 146 GST3146707LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
disk 1 0/1/1/1.0.0 sdisk CLAIMED DEVICE HP 146 GST3146707LC
/dev/dsk/c3t0d0 /dev/rdsk/c3t0d0

two disks of 146 GB

1. /dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
2. /dev/dsk/c3t0d0 /dev/rdsk/c3t0d0

Q.Use vgdisplay to determine which of the disks on your system are already members of
active volume groups. You should have at least one disk that isn’t currently in a volume group.
Note the free disk’s device filename; you will create a new volume group using your free disk
in the next part of the lab exercise

ans:bash-3.2# vgdisplay
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 10
Open LV 10
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 4384
VGDA 2
PE Size (Mbytes) 32
Total PE 4374
Alloc PE 3143
Free PE 1231
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

Q.Before adding a disk to a volume group, you may want to check the size of the disk. This is
accomplished via the diskinfo command. How large is your spare disk?

ans:

disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 146 GST3146707LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0

/dev/rdsk/c2t1d0 is the free disk where we create lvm

bash-3.2# diskinfo /dev/rdsk/c2t1d0
SCSI describe of /dev/rdsk/c2t1d0:
vendor: HP 146 G
product id: ST3146707LC
type: direct access
size: 143374744 Kbytes
bytes per sector: 512

bash-3.2# diskinfo -v /dev/rdsk/c2t1d0
SCSI describe of /dev/rdsk/c2t1d0:
vendor: HP 146 G
product id: ST3146707LC
type: direct access
size: 143374744 Kbytes
bytes per sector: 512
rev level: HPC1
blocks per disk: 286749488
ISO version: 0
ECMA version: 0
ANSI version: 3
removable media: no
response format: 2
(Additional inquiry bytes: (32)4b (33)53 (34)31 (35)32 (36)53 (37)4d (38)4c (39)20 (40)20 (41)20 (42)20 (43)20 (44)20 (45)20 (46)20 (47)20 (48)20 (49)20 (50)20 (51)f (52)0 (53)0 (54)60 (55)a (56)dc (57)b (58)59 (59)3 (60)1 (61)3 (62)22 (63)0 (64)0 (65)0 (66)0 (67)0 (68)0 (69)0 (70)0 (71)0 (72)0 (73)0 (74)0 (75)0 (76)0 (77)0 (78)0 (79)0 (80)0 (81)0 (82)0 (83)0 (84)0 (85)0 (86)0 (87)0 (88)0 (89)0 (90)0 (91)0 (92)43 (93)6f (94)70 (95)79 (96)72 (97)69 (98)67 (99)68 (100)74 (101)20 (102)28 (103)63 (104)29 (105)20 (106)32 (107)30 (108)30 (109)35 (110)20 (111)53 (112)65 (113)61 (114)67 (115)61 (116)74 (117)65 (118)20 (119)41 (120)6c (121)6c (122)20 (123)0 (124)0 (125)0 (126)0 (127)11 (128)17 (129)73 (130)30 (131)0 (132)0 (133)2 (134)0 (135)0 (136)0 (137)0 (138)0 )

II. Creating a Physical Volume, Volume Group, and Logical Volumes:::

1.Configure your free disk as an LVM physical volume
ans:

bash-3.2# pvcreate -f /dev/rdsk/c2t1d0
Physical volume "/dev/rdsk/c2t1d0" has been successfully created.

Q:Create a new vg01 volume group using your newly created physical volume

vgcreate -s 32 vg01 /dev/dsk/c2t1d0

Q Use vgdisplay and pvdisplay to check the status of your new physical volume and
volume group. How many physical volumes are in the volume group at this point? How many
logical volumes are in the volume group at this point? What is the extent size?

physical volumes- 1
logical volumes- 0
PE size -32 mb

bash-3.2# vgdisplay -v vg01
--- Volume groups ---
VG Name /dev/vg01
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 0
Open LV 0
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 4375
VGDA 2
PE Size (Mbytes) 32
Total PE 4374
Alloc PE 0
Free PE 4374
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Physical volumes ---
PV Name /dev/dsk/c2t1d0
PV Status available
Total PE 4374
Free PE 4374
Autoswitch On
Proactive Polling On

bash-3.2# pvdisplay -v /dev/dsk/c2t1d0
--- Physical volumes ---
PV Name /dev/dsk/c2t1d0
VG Name /dev/vg01
PV Status available
Allocatable yes
VGDA 2
Cur LV 0
PE Size (Mbytes) 32
Total PE 4374
Free PE 4374
Allocated PE 0
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On
Proactive Polling On

--- Physical extents ---
PE Status LV LE
00000 free 00000
00001 free 00000
00002 free 00000
00003 free 00000
00004 free 00000
00005 free 00000
00006 free 00000
00007 free 00000
00008 free 00000
00009 free 00000
00010 free 00000
00011 free 00000
00012 free 00000
00013 free 00000
00014 free 00000
00015 free 00000
00016 free 00000
00017 free 00000
00018 free 00000
00019 free 00000

Q: Create two 24-MB logical volumes in your new volume group. Name the first logical
volume cad and the second cam.

ans:

bash-3.2# lvcreate -L 24 -n cad /dev/vg01
Warning: rounding up logical volume size to extent boundary at size "32" MB.
Logical volume "/dev/vg01/cad" has been successfully created with
character device "/dev/vg01/rcad".
Logical volume "/dev/vg01/cad" has been successfully extended.
Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf

bash-3.2# vgdisplay -v vg01
--- Volume groups ---
VG Name /dev/vg01
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 4375
VGDA 2
PE Size (Mbytes) 32
Total PE 4374
Alloc PE 1
Free PE 4373
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg01/cad
LV Status available/syncd
LV Size (Mbytes) 32
Current LE 1
Allocated PE 1
Used PV 1

--- Physical volumes ---
PV Name /dev/dsk/c2t1d0
PV Status available
Total PE 4374
Free PE 4373
Autoswitch On
Proactive Polling On

since the size of the PE is 32mb, you need to atleast create a logical volume which is greater than or equals to 32 mb otherwise the LVM manager will be automatically rounded up to 32mb by extending the logical volume

bash-3.2# lvdisplay -v /dev/vg01/cad
--- Logical volumes ---
LV Name /dev/vg01/cad
VG Name /dev/vg01
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 32
Current LE 1
Allocated PE 1
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c2t1d0 1 1

--- Logical extents ---
LE PV1 PE1 Status 1
00000 /dev/dsk/c2t1d0 00000 current

Do an ll of the /dev/vg01 directory. What is the name of the volume group device file for
your new volume group? Each of your logical volumes should have two device files. Why?
ans:

bash-3.2# ll /dev/vg01
total 0
brw-r----- 1 root sys 64 0x010001 Dec 17 16:54 cad
brw-r----- 1 root sys 64 0x010002 Dec 17 17:03 cam
crw-r--r-- 1 root sys 64 0x010000 Dec 17 16:26 group
crw-r----- 1 root sys 64 0x010001 Dec 17 16:54 rcad
crw-r----- 1 root sys 64 0x010002 Dec 17 17:03 rcam

volume group device file: group (/dev/vg01/device)
same like disks, it has both ways of accessing as block device and as raw device that's why two device files per each lvm

Use SAM to remove your vg01 volume group in preparation for the next portion of this
lab. Volume groups can be managed in SAM from the Volume Groups object list:
SAM –> Disks and File Systems –> Volume Groups

To remove the volume group, first you need to delete all the lvms associated with that volume group

If you intend to use these disk(s) with the Veritas Volume Manager ¦ ¦
¦+--¦ you should first run /usr/sbin/pvremove on each of the device files ¦--+ ¦
¦¦ v¦ listed below. ¦ ^ ¦
¦¦ v¦ ¦ ¦
¦¦ ¦ /dev/rdsk/c2t1d0

pvremove /dev/rdsk/c2t1d0

Try a vgdisplay back at the command line to ensure the volume group is gone. Did SAM
remove the volume group device files, too?

yes.

How to extend the filesystem online

1. check either the machine is installed with jfs2 online
# swlist -l produst | grep -i online

2.check the size of file system
# bdf

3. check the size of available PE
# vgdisplay vg00

4. then extend the logical volume
# lvextend -L 4208 /dev/vg00/lvol5

5. next step is extend the file system
# fsadm -F vxfs -b 4208M /home

6. recheck the size
# bdf

# lvdisplay /dev/vg00/lvol5

More info: If you want to allocate extents from a specific disk (ex, c0t3d0) then use,

# lvextend -L 4208 /dev/vg00/lvol5 /dev/dsk/c0t3d0

If you don’t specify where LVM should allocate the new extents, LVM simply uses the first available extents in the volume group. After extending the logical volume, it’s a good idea to do an lvdisplay to see the result

How to extend the logical volume (without online)

How to increase the size of a logical volume without online JFS (advanced JFS)

** Please note that we can extend the logical volume online (without unmounting the mounted file system) by using fsadm command but for this, we need to have vertitas volume manager license should be installed. If you do not have the license, then go for without online option..

Note: the following example is using the volume group vg00 and the logical volume lvol4 (lvol4 is mounted on /tmp directory with 512 size, we are now going to increatse to 1 gb)

Check the volume group for enough space
vgdisplay vg00

Check the logical volume to determine if mirroring or striping is in effect
lvdisplay /dev/vg00/lvol4

1.lvextend -L 1024 /dev/vg00/lvol4 (82944)

vxlicense -p ( to see if veritas license installed or not, if not go for extendfs)

2. unmount the file system

umount /tmp ( i used lsof to list all files used by /tmp and kill them all)
lsof /tmp (find out PID and then kill -9 PID)
fuser -kc /tmp

3. extendfs -F vxfs /dev/vg00/rlvol4 ( please make to use character device file here)

4. mount /dev/vg00/lvol4 /tmp

5. bdf to see if this worked..

LVEXTEND on logical volume::::::::

commands that I performed on Hyderabad while extending /oradata...

/dev/vg00/lvol10 61440000 52192061 8675533 86% /oradata

# lvextend -L 82944 /dev/vg00/lvol10
# umount /oradata (it is giving resource busy error) try below
# fuser -kc /oradata (now unmount again)
# umount /oradata
# extendfs -F vxfs /dev/vg00/rlvol10
# mount /dev/vg00/lvol10 /oradata
# bdf

extending /ora10gdb on racg1(30) server

# lvextend -L 30000 /dev/vg01/lvol3
# umount /ora10gdb (it is giving resource busy error) try below
# fuser -kc /ora10gdb (now unmount again)
# umount /ora10gdb
# extendfs -F vxfs /dev/vg01/rlvol3
# mount /dev/vg01/lvol3 /ora10gdb
# bdf

TIPS:

How to determine if you have Online JFS

* swlist -l fileset | grep -i advanced

How to determine the filesystem type

* grep /tmp /etc/fstab
* Results should show the filesystem type (vxfs or hfs) in the return string

free disk:

disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 146 GST3146707LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0

HP -LVM How-to's in a Nut shell

pvcreate /dev/rdsk/c2t1d0
mkdir -p /dev/vg01
mknod /dev/vg01/group c 64 0x010000
vgcreate -s 32 /dev/vg01 /dev/dsk/c2t1d0
lvcreate -L 500 -n lvol1 /dev/vg01 ***** check if mirroring or striping required for this LVM. If mirroring or striping is required then there must be enough space available on multiple disks.

or
lvcreate -l 15 -n lvol1 /dev/vg01 (-l mean no of logical extents to be created for this, 15 * 32 = 480 mb)

create a file system vxfs:
#newfs -F vxfs /dev/vg01/rlvol1 ( make sure it is a character device file)

version 5 layout
524288 sectors, 524288 blocks of size 1024, log size 16384 blocks
unlimited inodes, largefiles not supported
524288 data blocks, 507712 free data blocks
16 allocation units of 32768 blocks, 32768 data blocks
For large file support::

(newfs -F vxfs -o largefiles /dev/vg01/rlvol1)

mkdir /testing
mount /dev/vg01/lvol1 /testing
bdf

vi /etc/fstab

/dev/vg01/lvol1 /testing vxfs delaylog 0 2

mount -a
or
mount -o remount /testing

III) How to add a disk to a Volume Group::

Note The following examples is using the disk c1t6d0 and the volume group vg01

1) Prepare the disk
pvcreate /dev/rdsk/c1t6d0

Note if the disk was previously used in another VG use the
following command instead:

pvcreate -f /dev/rdsk/c1t6d0

Note: Use caution when using pvcreate -f as this will
overwrite the existing volume group information on the disk.

2) Add the disk to the Volume Group
vgextend /dev/vg01 /dev/dsk/c1t6d0

IV) How to remove a Logical Volume::::

Note: the following example is using the volume group vg01 and the logical volume lvol1

1) Backup all user data
2) Umount the filesystem
umount /testing
3) remove the Logical volume
lvremove /dev/vg01/lvol1

V) How to reduce the size of a logical volume without online JFS (advanced JFS)

Note: the following example is using the volume group vg01 and the logical volume lvol1

1) Backup all user data
2) Umount the filesystem
umount /testing
3) Reduce the size
lvreduce -L 512 /dev/vg01/lvol1
Note: the new total size will be 512
4) Re-create the filesystem
newfs -F vxfs /dev/vg01/lvol1 (this will delete the data so you have already backed up)
5) Mount the Logical Volume:
mount /dev/vg01/lvol1 /testing
6) Restore the user data

VI) How to remove a disk from a volume group

Note: the following example is using the disk c1t6d0 and the volume group vg01

1) Make sure that the disk is not in use:
pvdisplay /dev/dsk/c1t6d0

Look at line starting with Allocated PE the number at the end
of the line should be 0. If it is not the disk is still in use

2) Remove the disk
vgreduce /dev/vg01 /dev/dsk/c1t6d0

More detailed commands,

1. check VG status by using
#vgdisplay -v

2. unmount the logical volumes on this VG

#umount /dev/vg00/lvol6
#umount /dev/vg00/lvol7

3. reduce the disk

#vgreduce /dev/vg00 /dev/dsk/c3t2d0

4. mount back the logical volume
#mount /dev/vg00/lvol6 /db1
#mount /dev/vg00/lvol7 /db2
5. check either the disk still exist or not
#vgdisplay -v

Combine 2 hard disk to become 1 vg

If your harddisk is small and you want to combine 2 harddisk to become 1 vg:

I think the first steps in this chapter will explain about this.

VII) How to remove a volume group

Note: the following example is using the volume group vg01 and the logical volume lvol1

1) Backup all user data
2) Find the name of all logical volume in this volume group
vgdisplay -v /dev/vg01
3) unmount all logical volumes
umount /lvol1
If you have other logical volumes, please unmount them all
4) Remove the volume group:
vgexport /dev/vg01

when I do this, I get the following error,
Beginning the export process on Volume Group "/dev/vg01".
vgexport: Volume group "/dev/vg01" is still active.

So, I made it inactive by,
vgchange -a n /dev/vg01

and then

vgexport /dev/vg01

Note: using vgexport to remove a volume group is easier and faster than using the vgreduce on each physical volume except the last one, followed by a vgremove. The other advantage is that the /dev/vg01 directory is also removed

OR another way to do,

* Remove all Logical Volumes
* Remove all disks except on using vgreduce
o This will need to be done for each disk in the volume group, except for the last disk
* remove the final disk in the volume group with vgremove

MORE INFORMATION ON HP-LVM :::::

Mirroring::

Mapping a logical extent to more than one physical extent. Logical volumes are mirrored, not disks.

Physical Extent (PE)

Unit used for allocating disk space to logical volumes, default size is 4MB. It is a set of contiguous disk blocks

Logical Extents (LE)
Logical extents are used to create the logical volume - they are the same size as physical extents

Striping
A logical volume that is configured to write across more than one disk in a stripe.

vgchange
Command used to change information about the volume group, such as to activate an inactive vg

man vgchange (will give more information and attributes)

vgexport

vgimport

How to inactive a volume group:::

#vgchange -a n /dev/vg01

Unmirroring a Logical Volume:::

#lvreduce -m 0 /dev/vg01/lvol7 (-m mirrior copy to 0 which mean the extents are mapped to only single disk)

Deactivating a Volume Group ::;

Umount all of the logical volumes in the volume group

Determine all of the mounted logical volumes by "bdf | grep vg01"

#vgchange -a n /dev/vg01

How to mirror a logical volume ::::

Note: Data mirroring is provided by an additionnal purchasable software product called MirrorDisk/UX

Note: the following example is using the volume group vg01 and the logical volume lvol7

To add a mirror to an existing logical volume:

lvextend -m 1 /dev/vg01/lvol7

Times USA and INDIA

2009-06-25T07:49:00.000-07:00

:::::::: Times USA and INDIA :::::::::::::

Kickstart Configuration in Linux...

2009-06-25T06:52:00.000-07:00

Red Hat Linux comes with a system for automatic installation called Kickstart. Instead of answering all the installation questions manually, including all the details of package selection, you can put your answers and list of packages into a file which will automatically be read by the installation program at startup. This can be very useful for installing a specific known configuration on a collection of machines, such as a grid cluster or a Beowulf cluster. It is also fairly easy to copy files or run shell scripts non-interactively to customize the installation.

OS: RHEL 4 ES.

The steps which I performed are described here.

We will make one server as kickstart server (172.16.17.43) that holds all the configurtion required for the installtion. We choose RHEL 4 ES box as kickstart server. We are going to perform these steps on this server now,,,

1. Install system-config-kickstart-2.5.16.1-1.noarch.rpm

#rpm -ivh system-config-kickstart-2.5.16.1-1.noarch.rpm

2.Using a X-manager tools like (WRQ reflection or X-Manager) to launch a graphical window to configure kickstart configuration.

as a x,

#system-config-kickstart

It displays the above dialogue box, and go through each configuration and set values as per your request. Once this is done,

click on File ---> Save File.

Save this file under (/kickstart/ks.cfg).

All the configuration now has been saved under ks.cfg file and you can edit it manually by using any text editor.

Now, we will export this file using NFS share make it available to all our hosts on the network.

# vi /etc/exports

/kickstart *(rw,sync)

Save and exit

#exportfs -r

# service nfs restart

# service portmap restart

# showmount --exports

Export list for ns1.testing.com:

/kickstart *

I hope this ends the kickstart server configuration...

Now go back to your work station where you would like to initiate the kickstart installation. Make sure to have the install media (CD #1) for this situation. Insert the CD and boot the machine. When it comes up, on RED HAT logo, type the following line..

linux ks=nfs:172.16.17.43:/kickstart/ks.cfg ksdevice=eth0 up

If you have DHCP configured for your env, the installation will choose a random IP for your work station/server. If you have choose the installation type as (CD) then you would need to insert all the remainig CD #2,3,4 depending on the software selection...

Compiling the Linux Kernel

2009-06-25T06:31:00.000-07:00

I never tried these steps but, got these from one of the blogs on the Internet for future reference.

1. Downloading the kernel source code.

In order to compile a new kernel we have to download the source code of the Linux kernel. We can download the source from http://www.kernel.org/. Here we can find all versions of the Linux kernel source code. Let's take an example. Suppose we want to compile the 2.6.9 version of the linux kernel. We have to download the 2.6.9 source code from:

http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.9.tar.bz2

It's better to download the bzipped version, as that will be more compressed than its gzipped counterpart; hence will take less time to download. A wget from the command line will look like:

wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.9.tar.bz2

Once we download the required kernel version source, we need to bunzip and untar it. We can do the following:

tar xvjf linux-2.6.9.tar.bz2

The 'x' option is to denote the untarring (e'x'traction), 'v' for verbose, 'j' for specifying that we need to bunzip the file before untarring and 'f' for stating the name of the input file.
The file will untar into the directory linux-2.6.9. Once it's untarred 'cd' to linux-2.6.9.

2. Configuring the kernel

We have to configure the kernel before we start compiling it. During the configuration phase, we will select the components which we want to be part of the kernel. For example: suppose we are using the ext3 filesystem. Then we need to select the ext3 filesystem support while configuring the kernel. Typically we have to run a

make menuconfig

This will bring up the ncurses interface for configuring the kernel. There are other options such as 'make xconfig' and 'make config'. The former will bring up the configuration menu in graphical mode and the latter in text mode.

Once we select the different components we want for our kernel, we can exit the configuration interface. We should select the option to save the configuration from the configuration menu, before exiting.

After we have configured the kernel as mentioned above, we can find a file named '.config' in the top level directory of the source. This file is the configuration file. It contains various options and their states (whether they are selected or not). For example, if we choose to have the PCI support in our kernel we can find an entry of the form:

CONFIG_PCI=y

in the .config file. Similarly, options which are selected as not required will appear as not set. Suppose we have not selected the XFS filesystem support in our kernel we will find the following in the .config

# CONFIG_XFS_FS is not set

A great feature of 2.6 kernels is that if we are running make menuconfig (or xconfig or config) for the first time, then the configuration menu we are presented with is based on our current kernel configuration. In my case, I have a Fedora Core 1 system. The kernel which I run is '2.4.22-1.2115.nptl'. Hence when I run a 'make menuconfig' for the first time on the source then the configuration menu presented will contain the options as given in '/boot/config-2.4.22-1.2115.nptl'.

3. Building Dependencies

This step is required in kernels prior to 2.6 series (here I am only referring to the stable series kernels). For example if we are using a 2.4 kernel then we have to build the dependencies explicitly. We have to run the following:

make dep

This will build the dependencies. But for a 2.6 kernel we can skip this step. The dependencies are automatically created when making the final image with a 2.6 kernel.

4. Creating the final image

We can build various types of kernel binary images. We can build a plain kernel image, or a compressed version of it; the usual choice is compressed, or the 'bzImage'. We can create the bzImage by running

make bzImage

In 2.6 kernels this step will also resolve the dependencies and proceed to create a bzImage image.
After the compilation is over we can find the kernel image at the path arch/i386/boot/bzImage in case of an image for a 386 based processor (Pentium, AMD etc.).

5. Compiling and Installing the modules

In the configuring section if we have selected some components to be built as kernel modules then we need to compile those modules. To compile the modules we should run the command:

make modules

This command will compile the components (which are selected for module compilation) to modules. In a 2.4 kernel the result will be .o files of the corresponding components. But in a 2.6 kernel the output file will be a .ko module. For example if we have given the option for the Network driver of Realtek cards to be built as modules then after giving a 'make modules' we can find in 'driver/net/' a file named 8139too.o in the case of a 2.4 kernel and 8139too.ko in the case of a 2.6 kernel.

After we have compiled the modules, it's time now to install the modules. To install the modules run:

make modules_install

as root. This will install the modules and other necessary files into the /lib/modules/2.6.9 directory

6. Booting from the new kernel

Once we are done with the installation of modules, we can go for an automatic installation procedure for the kernel binary. We just have to run

make install

This will update the kernel image on to the /boot area, update the configuration file of the bootloader (lilo.conf or grub.conf) and then do the necessary actions to make the new kernel bootable.

After this we need to reboot the machine. When the machine boots next time the boot menu will present us with the option to boot from the new kernel we built. We choose that option and voila!! boot into a kernel we built all by ourselves

7. Manual installation of the kernel

In case 'make install' does not work, or if we cannot perform an automatic installation due to some other reason, we can go for a manual installation of the kernel. For example, if we are using the grub boot loader then we have to copy the bzImage into the boot partition and then change the '/etc/grub.conf' to reflect the presence of the new image. If we are having lilo boot loader then we have to copy the bzImage to the boot location and then modify the lilo.conf and then run the 'lilo' command to make sure that next time we boot we will have our new image as a choice to boot from. The following are the steps we should perform as root user if we are using lilo boot loader:

cp -a arch/i386/boot/bzImage /boot/bzImage-2.6.9

After this we add the following entry to /etc/lilo.conf

image=/boot/bzImage-2.6.9
label=2.6.9-kernel
root=your_root_disk

We should run lilo after this
lilo -v

We will reboot the machine after this. When we are prompted at the lilo prompt enter '2.6.9-kernel' as the boot option and we will be booting to the new custom built kernel

8. Cleaning the kernel source

After we have initiated compilation once on the source if we want to clean the object files and other temporary files then we have to run the following:

make clean

This will remove most generated files but will keep the configuration file.
If we need an absolute cleaning, i.e. if we want to return the source to the state in which it was before we started the compilation, then do a

make mrproper

This command will delete all generated files, the configuration file as well as various backup files. This will in effect unwind all the changes we made to the source. The source after this step will be as good as it was just after the download and untar

2009-06-25T05:47:00.000-07:00

::::: Setting up a DNS Server in Linux (RHEL 4 ES up 2) ::::

In this example, we are using
172.16.17.43 - ns1.testing.com
172.16.17.52 - ns2.testing.com
172.16.17.19 - testing.com (or a www web server) and also a mail server

Before configuring DNS services, you need to edit , /etc/resolv.conf as
nameserver 127.0.0.1
and restart network services

Packages needed....
rpm -ivh bind-9.2.4-2.i386.rpm bind-chroot-9.2.4-2.i386.rpm bind-devel-9.2.4-2.i386.rpm
There are other two packages also needed but they alredy installed on the machine (bind-utils, bind-libs)

Once the packages are installed, go the configuration file
[root@lnxtestsrv1 named]# vi /var/named/chroot/etc/named.conf
// Default named.conf generated by install of bind-9.2.4-2
options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
};
include "/etc/rndc.key";
# these are the extra lines that I added to the file..
zone "testing.com" {
type master;
file "testing.com.zone";
allow-update { none; };
};
zone "17.16.172.in-addr.arpa"{
type master;
file "1.16.172.in-addr.arpa.zone";
allow-update { none; };
};
then go to cd /var/named/chroot/var/named/
create two files (forward and reverse look up). In our case forward lookup is, testing.com.zone and reverse look up is, 1.16.172.in-addr.arpa.zone
vi testing.com.zone
$TTL 86400
@ IN SOA testing.com. (
root
2007112800
21600
1800
604800
900 )
IN NS ns1.testing.com.
IN NS ns2.testing.com.
IN MX 10 mail.testing.com.
IN A 172.16.17.19
ns1 IN A 172.16.17.43
ns2 IN A 172.16.17.52
mail IN A 172.16.17.19

Save the file and exit...
Then create a reverse lookup file that we defined in named.conf
# vi 17.16.172.in-addr.arpa
$TTL 86400
@ SOA testing.com. (
root
2007112800
21600
1800
604800
900
)

19.17.16.172.in-addr.arpa. IN PTR testing.com.
43.17.16.172.in-addr.arpa. IN PTR ns1.testing.com.
19.17.16.172.in-addr.arpa. IN PTR mail.testing.com.
52.17.16.172.in-addr.arpa. IN PTR ns2.testing.com.

Save the file and exit...
Now, we will restart the named service
#service named restart
#chkconfig --level 345 named on ( t0 bring up the service online for every reboot )
Let us check the configuration errors or any syntax errors...
#named-checkconf /var/named/chroot/etc/named.conf
#named-checkzone testing.com /var/named/chroot/var/named/testing.com.zone

zone testing.com/IN: loaded serial 2007112800 OK

Done!!!!!!

Now testing....
[root@lnxtestsrv1 named]# dig @localhost +short A testing.com
172.16.17.19
[root@lnxtestsrv1 named]# dig @localhost +short NS testing.com
ns1.testing.com.
ns2.testing.com.
[root@lnxtestsrv1 named]# dig @localhost +short MX testing.com
10 mail.testing.com.
[root@lnxtestsrv1 named]# dig @localhost +short ns1.testing.com
172.16.17.43
[root@lnxtestsrv1 named]# dig @localhost +short mail.testing.com
172.16.17.19
[root@lnxtestsrv1 named]# dig @localhost +short testing.com
172.16.17.19
#dig @localhost +short -x 172.16.17.43ns1.testing.com

::::: Setting up a Seconday / Slave DNS server:::::

Before configuring DNS services on Secondary DNS server, you need to edit , /etc/resolv.conf as

nameserver 127.0.0.1

and restart network services

It requires the same packages of what primary DNS server has..
Configuring the slave nameserver is fairly simple once you have your master nameserver set up correctly.
Go to,
/var/named/chroot/etc/named.conf
options{
directory "/var/named/";
};
zone "testing.com" IN {
type slave;
masters { 172.16.17.43; };
file "slaves/testing.com.zone";
};
As you can see all we did was set up our testing.com zone as type slave and pointed to the master server and where we want to store the zone files (we don't manually create them).
Now start the service and make sure it comes up on a reboot.

# service named start
# chkconfig named on

The DNS primary and seconday configuration is complete... You can go to the client machines and edit the /etc/resolv.conf

nameserver 172.16.17.43

nameserver 172.16.17.52

Restart the network service (service network restart), try resolving it.

New Day.... New Blog

2009-06-25T05:39:00.000-07:00

This blog describes me about my work, articles and day-to-day activities that I do, just like other blogs. So, keep watching my blog and provide any feedback or suggestions

Thanks
-Shankar