Showing posts with label Redhat Linux. Show all posts
Showing posts with label Redhat Linux. Show all posts

Monday, May 20, 2013

Redhat- How to find the Hardware Model on linux ?


Dmidecode reports information about your system's hardware as described in your system BIOS according to the SMBIOS/DMI standard

#dmidecode

This information typically includes system manufacturer, model name, serial number, BIOS version, asset tag as well as a lot of other details of varying level of interest and reliability depending on the manufacturer. This will often include usage status for the CPU sockets, expansion slots (e.g. AGP, PCI, ISA) and memory module slots, and the list of I/O ports (e.g. serial, parallel, USB).

Redhat Linux - How to for GFS Filesystems

How-to for GFS Filesystems

You can use either of the following formats to create a clustered GFS file system:
#gfs_mkfs -p lock_dlm -t ClusterName:FSName -j Number BlockDevice
#mkfs -t gfs -p lock_dlm -t LockTableName -j NumberJournals BlockDevice

You can use either of the following formats to create a local GFS file system:
#gfs_mkfs -p lock_nolock -j NumberJournals BlockDevice
#mkfs -t gfs -p lock_nolock -j NumberJournals BlockDevice

At each node, mount the GFS file systems. For more information about mounting a GFS file
Command usage:
mount BlockDevice MountPoint
mount -o acl BlockDevice MountPoint
The -o aclmount option allows manipulating file ACLs. If a file system is mounted without the -o acl mount option, users are allowed to view ACLs (with getfacl), but are not allowed to set them (with setfacl).

Formatting the logical Volume
#gfs_mkfs -p lock_dlm -t alpha:mydata1 -j 8 /dev/vg01/lvol0

The gfs_jadd command must be run on mounted file system, but it only needs to be run on one node in the cluster. All the other nodes sense that the expansion has occurred.

#lvextend -L +80G /dev/vgcl_gfs_san_eos/vol01_lv
#gfs_grow -v /dev/vgcl_gfs_san_eos/vol01_lv /db/eospr1/vol01

Sunday, May 19, 2013

Redhat Linux -Troubleshooting SAN Lun unavailability and HBA Issue


First , we will try to understand the Scenario  Suppose the LUN is coming from a storage and it is being used on Redhat Linux in LVM. Now when you run df -k, you see errors.

#df -k - This gives an error on the filesystem

Run pvs  -This will give us the details of the disk.
Look at the left column of PV, this will give you the details disks present in the volume group vgora

#pvs

  PV              VG     Fmt  Attr PSize   PFree
  /dev/emcpoweray vgora  lvm2 a--  101.15G    0
  /dev/emcpowerx1 vgora  lvm2 a--  139.70G 9.70G
  /dev/sda2       vgroot lvm2 a--   31.97G    0

Check the details of the HBA
a. HBA Port state
root@test1: # cat /sys/class/fc_host/host1/port_state
Online

b. HBA speed 
root@test1: # cat /sys/class/fc_host/host1/speed
4 Gbit

c.Port Name -WWPN
root@test1: # cat /sys/class/fc_host/host1/port_name
0x20010024e859e129

d.Node Name -WWNN
root@test1: # cat /sys/class/fc_host/host1/node_name
0x20000024e859e129

Provide the required info to the Storage team and they may help you to resolve the problem.