Installing HBAs/Drivers on an Linux Host

 

Topic

Setting up a host environment

Selections

Select a host: Linux

Select a Linux task: Installing HBAs/drivers

Select a HBA type: QLogic

Select a switch type: Brocade

 

 

Contents

·             Installing QLogic HBA(s) on a Linux host 4

·             Updating QLogic HBA firmware for Linux. 4

·             Enabling an in-kernel QLogic driver for Linux. 9

·             Downloading latest QLogic driver for Linux. 10

·             Installing a QLogic HBA driver on Linux host 12

·             Determine WWN of new HBA for Linux. 16

·             Creating switch zones. 16

·             Making LUNs or Devices available to Linux. 18

 


 

Install/Setup QLogic HBA/Driver Environment on Linux

Using various procedures, this document for Linux, featuring a QLogic HBA environment describes how to install and setup host bus adapters and other aspects of a host environment that deal with managing devices of a storage system. A series of procedures take you from installing HBAs, to installing and setting up HBA firmware and drivers.

 

 

·        Installing QLogic HBA(s) on a Linux host

 

Overview

This procedure describes how to install HBAs on a Linux host.

 

This procedure is based on content from the following EMC manuals:

  • EMC Host Connectivity Guide for Linux
  • EMC Support Matrix Linux (RHEL or SuSE)

 

You can download these guides from EMC Online Support (registration required): https://support.EMC.com

 

 

 

1.   

Install Adapter in card slot

With host system power removed, install the HBA(s) by following the instructions included with your adapter. The adapter installs into a single slot and has no user-configurable jumpers or switches.

 

Repeat the installation steps for each host in which you are installing Fibre Channel HBAs.

 

 

 

 

 

 

 

 

2.   

Apply power and boot

Reapply power and allow the system to boot normally.

 

 

 

7Table of Contents

 

·        Updating QLogic HBA firmware for Linux

 

Overview

This procedure describes how to update the QLogic HBA firmware on a Linux host.

 

This procedure is based on content from the following EMC manuals:

  • EMC Host Connectivity Guide for Linux
  • EMC Support Matrix Linux (RHEL or SuSE)

 

You can download these guides from EMC Online Support (registration required): https://support.EMC.com

 

Ensure that the HBA firmware (FCode) is current on the adapter before proceeding with other host setup tasks.

 

 

1.   

Verify Current Firmware

Verify the correct BIOS version is present after the HBA is installed:

Note:  Refer to the E-Lab Interoperability Navigator (ESM) for required BIOS versions for qualified HBAs.

a.     As the host is booting, watch for the QLogic banner.  As soon as the QLogic banner appears, press Qtrl-Q to enter Fast!Util.

b.    Select Configuration Settings from the Fast!Util Options menu.

c.     Select Adapter Settings from the Configuration Settings menu.

d.    Under Adapter Settings, note the BIOS version.

e.     Perform one of the following depending on the BIOS version:

·            If the version displayed is not the required version, proceed to the next step to upgrade the QLogic HBA BIOS and then continue to set the data rate and topology (if necessary).

·            If the version displayed is the required version, skip the next step to upgrade the QLogic HBA BIOS and then continue to set the data rate and topology (if necessary).

 

 

2.   

Upgrade the BIOS if required:

Upgrade the QLogic HBA BIOS (if necessary):

 

There are three methods that can be used to upgrade the HBA BIOS (instructions follow below):

 

·         QLogic SANsurfer

·         QLogic SANsurferCLI

·         NVRAM file on a DOS-bootable diskette

 

 

Using QLogic SANsurfer:

 

The SANsurfer GUI may be downloaded from the EMC-approved section of the QLogic website at http://www.qlogic.com.  Click Downloads on the left side of the screen.  Click the EMC link under OEM Models.  On the next page, select EMC SYMMETRIX, CLARiiON, & CELERRA supported software.  Select the HBA model in the Product column of the table.  On the next table, find the correct SANsurfer file and click the associated Download link.


To update the BIOS using the SANsurfer, refer to the QLogic provided documentation on their website for detailed instructions.

To invoke the GUI, run the following command from a terminal window:

/opt/QLogic_Corporation/SANsurfer/SANsurfer &

Note:  When upgrading the BIOS for QLogic 4GB HBAs, the minimum required version of the QLogic SANsurfer GUI is 2.0.30b52.

 

 

 

Using QLogic SANsurferCLI:

 

The SANsurferCLI (scli) is installed as part of the qlinstaller or may be downloaded from the EMC-approved section of the QLogic website at http://www.qlogic.com.  Click Downloads on the left side of the screen.  Click the EMC link under OEM Models.  On the next page, select EMC SYMMETRIX, CLARiiON, & CELERRA supported software.  Select the HBA model in the Product column of the table.  On the next table, find the correct SANsurfer file and click the associated Download link.


To update the BIOS using the SANsurferCLI, refer to the QLogic provided documentation on their website for detailed instructions.

To invoke the CLI, run the following command:

/opt/QLogic_Corporation/SANsurferCLI/scli

Note:  When upgrading the BIOS for QLogic 4GB HBAs, the minimum required version of the QLogic SANsurfer CLI is 1.06.16 build 23.

 

 

 

Using the NVRAM file on a DOS-bootable diskette:

 

a.      Obtain the latest version of the BIOS from the QLogic Website at http://www.qlogic.com.  Click Downloads on the left side of the screen.  Click the EMC link under OEM Models.  On the next page, select EMC SYMMETRIX, CLARiiON, & CELERRA supported software.  Select the HBA model in the Product column of the table.  On the next table, find the correct BIOS file and click the associated Download link.

b.      The file is a self-extracting .zip file that must be extracted to a bootable diskette drive by inserting a diskette into a Microsoft Windows 9x machine.  Open any DOS window and at the DOS prompt, format the diskette by entering the following command:

format /s a:

At the DOS prompt, change (cd) to the directory in which you saved the zipped file and extract the file to the diskette.

c.      Verify the QLogic HBA(s) are installed in the host before proceeding.

d.      Insert the BIOS upgrade installation diskette into the floppy drive.

e.      Reboot the host.

f.       After the host has rebooted, a DOS prompt appears.  Type flasutil /L /F and press Enter.

Note:  The HBA BIOS upgrade might take a few minutes.

After the upgrade is complete, remove the diskette and reboot the host.  During startup, the QLogic banner should display the required BIOS version.

 

3.   

Set BIOS/NVRAM parameters:

EMC requires configuring the QLogic BIOS settings with the EMC-approved NVRAM settings file.  This file contains all of the BIOS settings for the QLogic adapters that have been tested and approved for connection to EMC storage arrays. 

 

Note:  Refer to the E-Lab Interoperability Navigator (ESM) for required NVRAM versions for qualified HBAs.

 

For a complete list of the QLogic parameters and their pre-configured EMC settings, refer to the appropriate EMC Fibre Channel with QLogic Host Bus Adapters for the Linux Environment manual for your driver version (manuals are available on www.qlogic.com).

 

These settings are configurable in NVRAM using the Host Adapter Settings, Advanced Settings, and Extended Firmware Settings menus.

 

 

4.   

Modify HBA settings

The EMC default setting for the data rate on the QLA23xx and QLE23xx HBAs is Auto Select mode.  However, it is recommended to hard code the exact rate to the HBA port speed. For example, set the rate to 4 GB on 4GB-capable QLA246x/QLE246x series.

 

Note:  For any device connected to the HBA, set the device data rate (if applicable) before setting the HBA data rate.

 

Perform these steps for each QLogic HBA to be modified:

 

a.     Boot the host and when the QLogic banner appears, press Ctrl-Q enter Fast!Util.

b.    Select Configuration Settings from the Fast!Util Options menu.

c.     Select Host Adapter Settings from the Configuration Settings menu.

d.    Select the Data Rate setting and press Enter.

e.     Select the appropriate speed for the device to which the QLogic HBA will connect.  The options are 0 for 1GBs, 1 for 2GBs, and 2 for Auto Select.

f.     Press ESC to return to the Fast!Util Options menu.

g.    When prompted to save the changes made to the current adapter, select Save Changes.

h.     Repeat the steps above (starting at step b) for each adapter.

i.      Press ESC to exit Fast!Util.

j.      Reboot the host.

 

 

5.   

Modify the HBA topology settings:

The EMC default setting for the topology is set to 2 (loop preferred; otherwise point to point).  For Linux environments, it is recommended that the Connection Options parameter be set to 1 when attached to a fabric and to 0 when attached to an EMC storage array directly.

 

If necessary, the topology value can be changed as follows:

 

a.     Reboot the host, if necessary, and when the QLogic banner appears, press Qtrl-Q to enter Fast!Util.

b.    Select Configuration Settings from the Fast!Util Options menu.

c.     Select Host Adapter Settings from the Configuration Settings menu.

d.    Select Connection Options and press Enter.

e.     Select the appropriate topology and press Enter:

·         For a direct connect environment: Set to 0 (loop only)

·         For a switch environment: Set to 1 (point to point only)

f.     Press ESC to return to the Fast!Util Options menu.

g.    When prompted to save the changes made to the current adapter, select Save Changes.

h.     If you have more adapters to configure, choose Select Host Adapter and repeat the steps above (starting at step b) for each adapter.

i.      Press ESC to exit Fast!Util.

Reboot the host.

 

 

7Table of Contents


 

·        Enabling an in-kernel QLogic driver for Linux

 

Overview

This procedure example for RHEL 4 Linux describes how to grab an appropriate QLogic driver from the in-kernel register and to enable and assign it to the specific HBA. Then build RAM disk including the driver. If driver entry is not available within the Linux kernel, then go to the next set of procedures.

 

IMPORTANT:  Refer to the E-Lab Interoperability Navigator (ESM) for specific qualified kernel versions and distributions.  The support stated in the E-Lab Interoperability Navigator (ESM) supersedes versions listed in this document.

 

This procedure is based on content from the following EMC manuals:

  • EMC Host Connectivity Guide for Linux
  • EMC Support Matrix Linux (RHEL or SuSE)
  • EMC Fibre Channel with QLogic Host Bus Adapters for Linux Environment

 

You can download these guides from EMC Online Support (registration required): https://support.EMC.com

 

 

1.   

Engage the appropriate HBA driver

To engage an HBA driver:

Ensure that the /etc/modprobe.conf file references an entry for each installed QLogic HBA.

 

Fore each installed QLogic HBA, add an entry:

 

alias scsi_hostadapterN qla2xxx

 

Where N is the sequential value of each QLogic HBA installed in the system, beginning with the number after the last host adapter number entry in the file. The first host bus adapter entry begins with zero and qla2xxx is the driver name for the adapter.

 

For example:

 

alias scsi_hostadapter1 qla2100

alias scsi_hostadapter1 qla2200

alias scsi_hostadapter1 qla2300

alias scsi_hostadapter1 qla2322

alias scsi_hostadapter1 qla2400

alias scsi_hostadapter1 qla6312

 

 

2.   

Create RAM disk:

Whenever /etc/modprobe.conf is modified, a new ramdisk should be created to reflect the changes made. Create a new ramdisk image to include the newly added references to the QLogic HBAs:

 

cd /boot

mkinitrd –v initrd-$1.img $1

 

Where: $1 is the v2.6.x kernel version currently running.

For example:

 

mkinitrd –v initrd- 2.6.9-55.ELsmp.img 2.6.9-55.ELsmp

 

 

3.   

Reboot

Reboot the host.

 

 

 

7Table of Contents

 

 

·        Downloading latest QLogic driver for Linux

 

Overview

This procedure describes how to grab the latest QLogic driver software from the QLogic website.

 

IMPORTANT:  Refer to the E-Lab Interoperability Navigator (ESM) for specific qualified kernel versions and distributions.  The support stated in the E-Lab Interoperability Navigator (ESM) supersedes versions listed in this document.

 

Note the following for QLogic v8.x-series drivers:

 

·         Only the QLogic v8.01.xx driver provides support for the 4 GB capable QLA24xx/QLE24xx-series HBAs, not the v8.00.xx driver.

·         The QLogic v8.xx.xx driver is supported on QLA23xx/QLE23xx-series HBAs for RHEL 4.0, RHEL 4.0 U1, and SLES 9 SP1 hosts.

The QLogic v8.01.06 driver introduces support for the 4 GB capable QLA24xx/QLE24xx-series HBAs. The v8.01.06 driver is supported only on RHEL 4.0 U2 and SLES 9 SP2 at this time.

When installing or upgrading drivers, be sure to use the latest versions specified by EMC. Review the E-Lab Interoperability Navigator (ESM) for the latest information on approved HBAs and drivers.

 

 

4.   

Download the HBA driver

To download the latest HBA driver:

a.   Create a directory to which you will save the driver.  For example:

mkdir /qlogic_driver

b.      Use a web browser to access the QLogic website at

http://www.qlogic.com.

 

c.      Click Downloads at the left side of the screen.

d.      Click the EMC link under OEM Models.

e.      On the next page, select EMC SYMMETRIX, CLARiiON, & CELERRA supported software. 

f.       Select the HBA model in the Product column of the table. On the next table, find the supported driver and click the associated Download link. 

g.      Extract the downloaded file to the directory created earlier.

 

 

 

7Table of Contents


 

·        Installing a QLogic HBA driver on Linux host

 

Overview

This procedure describes how to install the QLogic driver on a Linux host. It uses, for illustration purposes, a version 8.0.x driver version for out of kernel (2.6) installation.

 

Refer to the release notes provided with the driver for information that might be unique to new driver revisions.

 

 

1.   

Install prep:

Prior to installing the QLogic driver, processes holding the driver open must be stopped so that the currently loaded driver can be removed from the running kernel.  Perform the following steps prior to the installation:

a.     Stop all I/O.

b.    Unmount all filesystems attached to the QLogic driver.

c.     If PowerPath is installed and enabled on the host, then the PowerPath service must be stopped.  To stop the PowerPath service, type one of the following commands:

 

/etc/init.d/PowerPath stop

or:

service PowerPath stop

d.    If the QLogic SANsurfer daemon qlremote is installed and enabled on the host, stop the qlremote service so the driver can be removed from the currently running kernel.  To stop the qlremote service, type one of the following commands:

 

/etc/init.d/qlremote stop

or:

service qlremote stop

 

e.  

Install the driver

Install the QLogic v8.xx.xx driver onto a Linux host platform using one of the following methods (instructions follow below):

 

·         Method One - To use the QLogic DKMS RPM to compile and install the modular driver for Dell servers running RHEL 4.0 systems and attached to EMC storage systems, refer to METHOD ONE:  Installing the QLogic v8.xx.xx driver via the QLogic DKMS RPM below.

This method requires no manual edits for Dell servers attached to EMC storage systems.  By installing the DKMS RPM, the necessary files will be edited and the driver will be compiled and installed automatically.

·         Method Two – To use the QLogic RPM to compile and install the modular driver for RHEL 4, SLES 9, and SLES 10, refer to METHOD TWO:  Installing the QLogic v8.xx.xx driver via the QLogic Installation Script below.

This method requires no manual edits for systems attached to EMC storage systems.  By installing the QLogic RPM, the necessary files will be edited and the driver will be compiled and installed automatically.

 

 

f.  

Select the directory

Installation instructions for QLogic v8.xx.xx driver:

 

METHOD ONE:  Installing the QLogic v8.xx.xx driver via the QLogic DKMS RPM:

 

This section guides you through the process of installing and utilizing the DKMS RPM for Dell servers running the RHEL 4.0 distribution.  The DKMS RPM will build and install the QLogic driver modules and will modify the /etc/modprobe.conf file with the entries similar to the following:

options qla2xxx ql2xfailover=0
alias scsi_hostadapter2 qla2100
alias scsi_hostadapter3 qla2200
alias scsi_hostadapter4 qla2300
alias scsi_hostadapter5 qla2322
alias scsi_hostadapter6 qla6312


The following are example steps to integrate the QLogic driver.  Also refer to the Readme file in the driver package.

a.     Boot into the qualified and supported kernel onto which the driver will be installed.

b.    Verify you have obtained the qla2xxx-v8.xx.xx1-2dkms.tgz package from the EMC-approved section of the QLogic website as instructed earlier.

c.     Uncompress and extract the source files from the tar archive:

[root@l82bi205 extra]# tar zxvf
qla2xxx-v8.xx.xx-2dkms.tar.gz


The initial decompression will provide you with the following:

qla2xxx-v8.xx.xx-2/
qla2xxx-v8.xx.xx-2/qla2xxx-v8.xx.xx-2dkms.noarch.rpm
qla2xxx-v8.xx.xx-2/dkms-2.0.5-1.noarch.rpm
qla2xxx-v8.xx.xx-2/README.dkms


d.    Install the DKMS RPM:

cd qla2xxx-v8.xx.xx-2
rpm -ivh dkms-2.0.5-1.noarch.rpm

Preparing...
   ########################################### [100%]
   1:dkms
   ########################################### [100%]


e.     Install the QLogic driver RPM:

rpm -ivh qla2xxx-v8.xx.xx-2dkms.noarch.rpm

Preparing...
   ########################################### [100%]
   1:qla2xxx
   ########################################### [100%]


The console output reported by the RPM driver installation will appear.

A new
ramdisk will be created automatically by the DKMS RPM installation.

f.     Reboot the host.

 

 

METHOD TWO:  Installing the QLogic v8.xx.xx driver via the QLogic Installation Script:

 

This section guides you through the process of installing and utilizing the QLogic installation script for RHEL 4.0 and SLES 9 SP1 distributions.  The script will build and install the driver and will modify the /etc/modprobe.conf file on RHEL 4.0 hosts and the /etc/modprobe.conf.local and /etc/sysconfig/kernel files on SLES 8 hosts.

NOTE:  By default, the installation script will install the QLogic HBA SNIA API libraries and the SANsurferCLI.

The following are example steps to install the QLogic driver via the installation script.  Also refer to the Readme file in the driver package.

a.     Boot into the qualified and supported kernel onto which the driver will be installed.

b.    Verify you have obtained the qlafc-linux-8.xx.xx-1-install.tgz package from EMC-approved section of the QLogic website as instructed earlier.

c.     Uncompress and extract the source files from the tar archive:

tar zxvf qlafc-linux-8.xx.xx-1-install.tgz

The initial decompression provides the following:

qlafc-linux-8.xx.xx-1-install/
qlafc-linux-8.xx.xx-1-install/scli-1.06.16-18.i386.rpm
qlafc-linux-8.xx.xx-1-install/set_driver_param
qlafc-linux-8.xx.xx-1-install/qla2xxx-v8.xx.xx-1.noarch.rpm
qlafc-linux-8.xx.xx-1-install/qlinstall
qlafc-linux-8.xx.xx-1-install/README.qlinstall
qlafc-linux-8.xx.xx-1-install/scli-1.06.16-18.ppc64.rpm
qlafc-linux-8.xx.xx-1-install/revision.notes
qlafc-linux-8.xx.xx-1-install/scli-1.06.16-18.ia64.rpm

d.    Install the QLogic driver via the installation script provided.  When using the -i option, the driver will be compiled, the current driver will be unloaded, and the newly compiled driver will be loaded into the kernel.

Note:  EMC does not support the persistent binding implementation contained within the QLogic driver.  As a result, it is recommended that the driver be compiled and installed without persistent binding enabled.  This can be accomplished by using the
dp option with the installation script.

Proceed with the installation.

cd qlafc-linux-8.xx.xx-1-install/./qlinstall -i –dp

The
qlinstall installation script provides the following features:

·         Installs the driver source RPM which installs the driver source code in the following path:

/usr/src/qlogic/<driver_version-rpm_release>

·         Builds and installs the QLogic driver and configuration module (qla2xxx_conf.o) for the QLogic HBA model(s) installed in the system.

·         Creates back-ups of important files and older drivers in the following directory:

/usr/src/qlogic/<driver version-rpm release>/backup

·         Automatically loads the driver for the HBA model present.

·         Builds and installs the ramdisk with the latest driver and configuration modules.

·         Installs the QLogic SNIA API Library V2.

·         Performs device discovery by default.

·         Provides the following command line options:

-    To invoke the device discovery at a later stage

-    To rebuild the ramdisk excluding or including QLogic HBA driver

-    To unload/load driver

-    To update the option ROM (BIOS, and so forth) on all HBAs

-    To update the NVRAM on all HBAs

-    To pass driver parameters.  For example, ql_port_down_retry (Overrides NVRAM default)

-    To invoke the SANsurferCLI (SCLI)
NOTE:  The SANsurferCLI (SCLI) is a command line interface that provides more flexibility for performing HBA configuration, device discovery, Option ROM and NVRAM updates, etc.

 

 

 

 

7Table of Contents

 

 

 

·        Determine WWN of new HBA for Linux

 

Overview

This procedure describes how to determine the WWN of the newly installed HBA.

 

 

1.   

Determine HBA WWN:

To determine the WWN of the newly installed HBA, at the command line use one of the following forms:

 

cat /proc/scsi/qla2300/# (instance number could be 0, 1, 2, 3,  …)

Or for Emulex:

cat /proc/scsi/lpfc/# (instance number could be 0, 1, 2, 3,  …)

This can also be verified by looking at the Fibre Channel Switch Port that the HBA is plugged in to.

 

 

 

7Table of Contents

 

·        Creating switch zones

 

Overview

For directions specific to Brocade switches, refer to the Brocade Fabric Manager Administrator’s Guide, which is located on Powerlink under the following location:

 

Home > Support > Documentation/White Paper Library > Hardware/Platforms Documentation > Connectrix Directors and Switches > Maintenance/Administration

 

Please refer to the section Managing Zones, which will provide the background information needed to configure and zone your fabric.

 

Note: There are multiple versions of the user guide available. Be sure to reference the version specific to your Fabric Manager version.

 

 

3.   

Create switch zones

Switch zones define paths between the host HBAs and the Symmetrix array and can be created using the switch management software (refer to the switch documentation).

 

Note:  If you are using an HP-UX server with QuickLoop zoning, then you must use port zoning.  Refer to EMC Knowledgebase article emc66355 for more information.

 

Definition -

Zoning is the process by which a single initiator is matched to a single storage array port (FA/SP) to be able to pass info to storage array device.

 

A Zone consists of 2 or more members, with only 1 initiator (HBA) per zone

A Zone is part of a zoneset .

A Zoneset is a collection of zones in a single fabric.

A Zoneset requires activation in order to be updated.

 

Important:  EMC Recommends single initiator zoning. To reduce the chance of data unavailability in the event that an HBA, switch, or FA Failure,  the host should have at least one primary path and one alternate path to each FA

 

 

4.   

Determine zoning configuration

Follow these steps to determine your zoning configuration:

a.      Determine the FA WWN by entering the following command:

symcfg –sid XXXX list –fa all

b.      Determine the HBA WWN by referencing the OS-specific commands from provisioning a host section.

c.      Determine the number of paths needed.

d.      Determine the Active Zone name.

The operations above must be performed on both fabrics for all FAs and HBAs.

 

5.   

Verify the HBA is logged in

Solutions Enabler offers a command line utility that will verify what is logged in to a specific Symmetrix FA. Use the following command:

 

symmask –sid SymmID –dir 3c –p 0 list logins

 

Where SymmID is the last four numbers of the Symmetrix serial number, 3c is the FA and 0 is the port on the FA.

 

It should also be noted that HBAs in an HP-UX host only show as logged in while there is active I/O.  However, if an entry exists in the login history table, it indicates that the HBA did log into the FA at some point.

 

After verifying that the host is logged in, move on to configuring the host.

 

 

7Table of Contents

 

 

·        Making LUNs or Devices available to Linux

 

Overview

This procedure describes how to make the devices or LUNs available or visible to a Linux host. It describes how to use the fdisk command to label and partition devices.

 

The Symmetrix devices will be represented in /proc/scsi/scsi and can be viewed by using:

 

more /proc/scsi/scsi.

 

Additional sd and sg filenames may need to be created because the number created by default in the kernel is usually less than 128 device filenames. 

 

Note and Caution: If your host system cannot see the devices, it may necessary to do a disk or device scan of the I/O bus with this procedure. If you must, at an appropriate low-peak time in your production environment, apply the necessary operating system native commands, to perform a device scan (discover) to make the devices visible to the host workstation. This might take a few minutes or so to execute. Be sure you follow your operating system specific administrators guide and/or known site procedures for this operation, as scanning devices can cause pauses and crashes to other operational processes running on this host. If you can and prefer, a reboot will also accomplish the same thing (device discovery). The following steps are provided only as a general or possible guide and not meant to supersede your site preferences.

 

 

6.   

Partition devices:

The fdisk command allows a single disk device to be partitioned. To partition the Symmetrix devices, verify that you are logged in as root and perform the steps below for each new device that requires partitioning as follows:

 

a.      Enter the following command:

fdisk /dev/<device_name>

where <
device_name> is the LUN device-name

For example:  fdisk /dev/sdb

b.      Type m (for help) and press Enter to display a menu of options.

Type
x (for expert functionality) and press Enter.  Type m and press Enter to see another menu of options.

c.      From the main fdisk menu, type n and press Enter to add a new disk partition.

d.      Type t and press Enter to change a partition’s system ID.

e.      Type L and press Enter for a list of hex codes for system Ids.  (Linux is type 83; Linux swap is 82.)

f.       Type p and press Enter to print the partition table so you can verify that the selections look correct.

g.      Type w and press Enter to write the table to disk and exit fdisk.

h.      Repeat steps c through g for each new Symmetrix device.

i.        If you want to display the partition numbers created after Linux recognizes them, view the file:

more / proc/partitions

 

 

7.   

Create filesystems on partitions:

Once each Symmetrix device has been formatted, partitions, and labeled, you must create a filesystem in order to make the partition useable.

 

To create a new filesystem:

 

a.   Enter the following mkfs command:

mkfs /dev/<device_name>/<partition_number>

where <device_name> is the LUN device name and <partition_number> is the partition number

Examples:

mkfs /dev/sdb1
mkfs –j/dev/sbd1
mkreiserfs –h r5 /dev/sdb1

b.      When prompted to confirm the construction of a new filesystem, type Y and press Enter.

 

 

8.   

Create mount directory:

Once the filesystem for each Symmetrix disk device has been created, you must create a mount directory for each device as follows:

 

mkdir /<mount_point>

For example:  

 

mkdir /mnt/sdb

 

where /mnt/sdb is the complete path for the new filesystem

 

 

9.   

Mount the file systems:

To mount each filesystem, enter the mount command as follows:

 

mount -t <filesystem type> /dev/<device_partition_name> <mount_point>

 

Examples:

 

mount –t ext2 /dev/sdb1 /mnt/sdb

mount –t ext3 /dev/sdb1 /mnt/sdb

mount –t reiserfs /dev/sdb1 /mnt/sdb

 

This mounts the partition /dev/sdb1 onto the mount point /mnt/sdb as the filesystem type specified.

 

This mount command is required every time the host is rebooted.  If preferable, the filesystem can be mounted automatically at boot time by adding this information to the /etc/fstab file.  Once the filesystems are mounted, data can be written to and read from them.

 

 

 

7Table of Contents