Making and Mounting the SAN Storage File Systems

After installing and configuring your SAN storage devices, follow this procedure to make and mount the SAN storage devices onto your cluster:




	Note: If the SAN volume was not presented to the host before the host was booted, you must use the SAN Management software to present the volume and reboot the host to proceed. If this is not done, any attempt to mount the volume results in an error message that states it is not a valid block device.

View the following file to determine the devices that are related to the SAN volumes available to the system:

# cat /proc/scsi/scsi

Command output looks similar to the following. In this example, lines containing Model: HSV110 indicate that the SAN was found on scsi2:

Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: HP 36.4G Model: MAN3367MC        Rev: HP05
  Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: COMPAQ   Model: HSV110 (C)COMPAQ Rev: 2003
  Type:   Unknown                          ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 00 Lun: 02
  Vendor: COMPAQ   Model: HSV110 (C)COMPAQ Rev: 2003
  Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 00 Lun: 03
  Vendor: COMPAQ   Model: HSV110 (C)COMPAQ Rev: 2003
  Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 01 Lun: 00
  Vendor: COMPAQ   Model: HSV110 (C)COMPAQ Rev: 2003
  Type:   Unknown                          ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 01 Lun: 02
  Vendor: COMPAQ   Model: HSV110 (C)COMPAQ Rev: 2003
  Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 01 Lun: 03
  Vendor: COMPAQ   Model: HSV110 (C)COMPAQ Rev: 2003
  Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 02 Lun: 00
  Vendor: COMPAQ   Model: HSV110 (C)COMPAQ Rev: 2003
  Type:   Unknown                          ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 02 Lun: 01
  Vendor: COMPAQ   Model: HSV110 (C)COMPAQ Rev: 2003
  Type:   Direct-Access                    ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 03 Lun: 00
  Vendor: COMPAQ   Model: HSV110 (C)COMPAQ Rev: 2003
  Type:   Unknown                          ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 03 Lun: 01
  Vendor: COMPAQ   Model: HSV110 (C)COMPAQ Rev: 2003
  Type:   Direct-Access                    ANSI SCSI revision: 02

Locate the device labels found at boot time:

# dmesg | grep "Attached scsi disk"
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi disk sdb at scsi2, channel 0, id 0, lun 2
Attached scsi disk sdc at scsi2, channel 0, id 0, lun 3
Attached scsi disk sdd at scsi2, channel 0, id 1, lun 2
Attached scsi disk sde at scsi2, channel 0, id 1, lun 3
Attached scsi disk sdf at scsi2, channel 0, id 2, lun 1
Attached scsi disk sdg at scsi2, channel 0, id 3, lun 1

Locate the entries in step 2 that correspond to the attached disks; the important numbers to match are those labeled lun in both step 2 and step 3.
Each SAN volume has two entries, and each SAN volume will have the same lun; in the output from step 3, sdb and sdd are both located on lun 2, on id 0 and id 1. Therefore, they correspond to the same SAN volume. Similarly, sdc and sde are on lun 3 and correspond to the same volume.
Both /dev/sdb and /dev/sdd contain the same data, and either can be mounted to access it.

Make the file system using the mke2fs command. HP recommends that you use the RAID option stride=. The calculation to determine the value of the stride option is (chunk size)/(sector size), where:

chunk size is the same as raid-sector size that you define in the SAN when you create a volume.
sector size is also called the inode size or the file system block size, and it is set to 4 KB in ext2 and ext3 file system types by default. You can change the value of the sector size parameter according to the limits specified in mke2fs( 8) .

See mke2fs( 8) for more information.

Partitioning of the SAN volumes is not currently supported, so each SAN volume is treated as a single contiguous space.

To make an ext3 file system, enter the following command, where /dev/sdb is the device name.

# mke2fs -j -R stride=n /dev/sdb

Command output looks similar to the following:

mke2fs 1.26 (03-Jan-2006)
/dev/sdb is entire device, not just one partition!
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
5128192 inodes, 10239780 blocks
511989 blocks (5.00%) reserved for the super user
First data block=0
313 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
         32768, 98304, 163840, 229376, 294912, 819200, 884736, 
1605632, 2654208, 4096000, 7962624

Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 20 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.

Create an empty directory to serve as the mount point for the SAN volume. In this example, /san is the directory name.
# mkdir /san
Mount the storage devices that contain valid file systems. In this example, /dev/sdb is the device name and /san is the mount point on the host:
# mount /dev/sdb /san

For information about exporting SAN storage to all nodes, see the HP XC System Software Administration Guide .

Making and Mounting the SAN Storage File Systems

Technical documentation

» Table of Contents

» Glossary

» Index