[gpfsug-discuss] GPFS Service Bulletin - July 5 2012

Scott Fadden sfadden at us.ibm.com
Thu Jul 5 17:25:22 BST 2012


Date Added: July 5, 2012
Issue:
IBM has identified an issue with GPFS file systems at versions 3.4 or 3.5 
which were migrated from file systems created with GPFS versions earlier 
than 3.4. This issue can occur only after using the mmmigratefs command 
with the [--fastea]option.
The issue can result in a loss of data, requiring the restoration of data 
from a backup source.
GPFS file systems created with versions earlier than 3.4 should not be 
migrated using the mmmigratefs command with the [--fastea] option until a 
fix is provided from IBM. IBM plans to make the fix available in GPFS 
versions
3.5.0.3 (APAR IV24151) and 3.4.0.15 (APAR IV24150). An ifix will also be 
available from IBM service.
If customers have already migrated file systems from GPFS versions earlier 
than 3.4, IBM service has a fix. Please follow the steps below to 
determine if your system may be affected.
To determine if your system may be affected:
1. Ensure your GPFS file systems are mounted.
2. As a user with GPFS administrator privileges on a machine where your 
GPFS file systems are mounted, issue the command:
        /usr/lpp/mmfs/bin/mmfsadm dump stripe | grep "inode 0"
The command will produce output that identifies locations for the "inode 
0" file for all currently
mounted GPFS file systems. Example output for a file system configured 
with two way meta-data
replication would be in the form:
        inode 0: 3:4098 1:4098
For a file system with no meta-data replication the output would be in the 
form:
        inode 0: 3:4098
The relevant information to look for to see if you may experience a 
problem are the fields denoting <disk>:<sector> for each inode 0 replica 
(e.g. 3:4098 and 1:4098 in these examples).
If each <disk>:<sector> replica only denotes 4098 for the sector field 
then you are not experiencing this problem. If however there is a number 
other than 4098 in the sector output then you are requested to immediately 
call IBM service and reference this problem. The IBM service person will 
walk you thru a fix for correcting the issue.


Scott Fadden
GPFS Technical Marketing 
Desk: (503) 578-5630 
Cell: (503) 880-5833 
sfadden at us.ibm.com
http://www.ibm.com/systems/gpfs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20120705/193c1254/attachment.htm>


More information about the gpfsug-discuss mailing list