Posts tagged ·

GPFS

·...

October 24, 2012 11:09 pm

Readme and Release notes for release 3.4.0.17 General Parallel File System 3.4.0.17 GPFS-3.4.0.17-power-AIX Readme

Comments Off
by    in AIX,Cluster

Readme and Release notes for release 3.4.0.17 General Parallel File System 3.4.0.17 GPFS-3.4.0.17-power-AIX Readme

 

 

After you have downloaded a GPFS for AIX update package into any directory on your system, use the following section to install the fix package.

  • - Collapse
    Installing a GPFS update for AIX 

    Complete these steps to install the fix package:

      1. Unzip and extract the BFF image(s) from the *.tar.gz file:

        gzip -d -c < filename >.tar.gz | tar -xvf -

      1. Verify the update’s BFF image(s) in the directory.

        Normally, the BFF images in the directory would be similar to the following:

        Unnnnnn
        .gpfs.base.bff

        Unnnnnn
        .gpfs.msg.en_US.bff

        Unnnnnn
        .gpfs.docs.data.bff

        gpfs.gnr

         

        where nnnnnn
        represents the six (6) digits of the PTF number for the BFF image.

        For specific filenames, check the Readme for the GPFS update by clicking the “View”
        link for the update on the Download tab.

    1. Follow the installation and migration instructions in your GPFS Concepts,
      Planning and Installation Guide.
  • - Collapse
    Upgrading GPFS nodes 

    In the below instructions, node-by-node upgrade cannot be used to migrate from GPFS 3.2 to later releases. For example, upgrading from 3.2.x.x to 3.4.y.y requires complete cluster shutdown, upgrade install on all nodes and then cluster startup.

    Upgrading GPFS may be accomplished by either upgrading one node in the cluster at a time or by upgrading all nodes in the cluster at once. When upgrading GPFS one node at a time, the below steps are performed on each node in the cluster in a sequential manner. When upgrading the entire cluster at once, GPFS must be shutdown on all nodes in the cluster prior to upgrading.

    When upgrading nodes one at a time, you may need to plan the order of nodes to upgrade. Verify that stopping each particular machine does not cause quorum to be lost or that an NSD server might be the last server for some disks. Upgrade the quorum and manager nodes first. When upgrading the quorum nodes, upgrade the cluster manager last to avoid unnecessary cluster failover and election of new cluster managers.

    1. Prior to upgrading GPFS on a node, all applications that depend on GPFS (e.g. Oracle) must be stopped. Any GPFS file systems that are NFS exported must be unexported prior to unmounting GPFS file systems. If tracing was turned on, then tracing must be turned off before shutting down GPFS as well.
    2. Stop GPFS on the node. Verify that the GPFS daemon has terminated and that the kernel extensions have been unloaded (mmfsenv -u
      ). If the command mmfsenv -u
      reports that it cannot unload the kernel extensions because they are “busy”, then the install can proceed, but the node must be rebooted after the install. By “busy” this means that some process has a “current directory” in some GPFS filesystem directory or has an open file descriptor. The freeware program lsof can identify the process and the process can then be killed. Retry mmfsenv -u
      and if that succeeds then a reboot of the node can be avoided.
    3. Upgrade GPFS using the installp command or via SMIT on the node.
tags: , ,
Comments Off
August 31, 2012 4:08 pm

DB2 managed GPFS cluster using db2cluster_prepare utility.

Comments Off
by    in Database

Question

This technote describes how to create a DB2® managed GPFS™ cluster using the db2cluster_prepare utility and how to clean the GPFS cluster manually from the DB2 pureScale™ environment.

Answer

Before you begin

  1. You must have installed IBM DB2 PureScale Feature for Enterprise Server Edition, Fixpack.
  2. Ensure that you have root access to use the db2cluster_prepare command.

About this task
In a DB2 pureScale environment, all data and logs must be on an IBM General Parallel File System (GPFS). You may need to create a DB2 managed GPFS cluster and file system. This can be done without an instance by using the db2cluster_prepare command.

Procedure

  • Create a new DB2 managed GPFS cluster file system.

    Perform these steps to create a DB2 managed GPFS cluster and file system on a host which has no previously existing GPFS cluster. This is the recommended method to setup a DB2 pureScale environment.

    a. Use the db2cluster_prepare command to create a DB2 managed GPFS.

     db2cluster_prepare -instance_shared_dev /dev/hdisk1

    b. Verify the GPFS cluster exists using the following commands. For example:

     /opt/IBM/db2/V9.8/instance/db2cluster –cfs –list –domain
    /opt/IBM/db2/V9.8/bin/db2greg -dump

    Example output:
    V,GPFS_CLUSTER,NAME,db2cluster_20110331115346.in.ibm.com,-,DB2_CREATED

  • Manually clean the DB2 Managed Cluster File System and uninstall GPFS

    a. The db2greg command will fail if you already have a GPFS_CLUSTER variable record
    in the global registry. You can remove the existing record using the following command:

    db2greg -delvarrec service=GPFS_CLUSTER

    b. Clean the GPFS from the system using the instructions in tech note 1447939

    http://www.aixmind.com/?p=2313

tags: , , ,
Comments Off
July 25, 2012 2:08 pm

GPFS failed to start up after installing patches

Comments Off
by    in AIX,Cluster

Problem:

 

After upgrading  GPFS from GPFS version 3.4.0.7 to 3.4.0.13 using smit update_all command, the GPFS failed to start up.

The following error message shows in /var/adm/ras/mmfs.log.latest file:

Loading kernel extension from /usr/lpp/mmfs/bin . . .
/usr/lpp/mmfs/bin/mmfskxload: /usr/lpp/mmfs/bin/aix64/mmfs64 is already loaded at 1352323072.
Fri Jul 20 09:26:37.413 2012: Error: daemon and kernel extension do not match.

 

Solution:

 

Actually, you should have run the mmfsenv -u to unload GPFS  kernel extensions. The README file with the patches has mentioned that:

 

a) Prior to upgrading GPFS on a node, all applications that depend on
 GPFS (e.g. Oracle) must be stopped. Any GPFS file systems that are
 NFS exported must be unexported prior to unmounting GPFS file systems.
 If tracing was turned on, then tracing must be turned off before
 shutting down GPFS as well.
b) Stop GPFS on the node. Verify that the GPFS daemon has terminated and
 that the kernel extensions have been unloaded (mmfsenv -u). If the
 command mmfsenv -u reports that it cannot unload the kernel extensions
 because they are "busy", then the install can proceed, but the node
 must be rebooted after the install. By "busy" this means that some
 process has a "current directory" in some GPFS filesystem directory or
 has an open file descriptor. The freeware program lsof can identify
 the process and the process can then be killed. Retry mmfsenv -u and
 if that succeeds then a reboot of the node can be avoided.
c) Upgrade GPFS using the installp command or via SMIT on the node.

 

Actually, you should be getting the following warning message when you install the patches using smit update_all or installp.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WARNING: An old MMFS/GPFS kernel extension is still loaded and cannot be unloaded. Please reboot before using newly installed version of product. !!!!!!

To solve  the issue if you forget to unload the kernel extension before patches installation.

 

1.  Unload the GPFS kernel extension:
mmfsenv -u

 

2. Restart GPFS cluster.

The updated kernel extension will be picked up.

Loading kernel extension from /usr/lpp/mmfs/bin . . .
/usr/lpp/mmfs/bin/aix64/mmfs64 loaded and configured.

 

tags: ,
Comments Off
Older Posts »