IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
1 reply Latest Post - ‏2012-07-10T15:25:11Z by
217 Posts

Pinned topic An issue using independent filesets and ACLs requires a fix

‏2012-07-09T13:21:34Z |
IBM has identified an issue with GPFS file systems at version 3.5 which currently use or have previously
used independent filesets and Access Control Lists (ACLs). This issue can occur if independent filesets
have been created with the mmcrfileset --inode-space command and any files or directories in the GPFS
file system have ACLs added or modified with commands such as mmputacl or mmeditacl. File systems
which have previously used but have now deleted independent filesets are still susceptible to this issue.

The issue can result in a loss of data access to any file or directory within the GPFS file system which has
an ACL.

IBM plans to make a fix available in GPFS version (APAR IV24426). An ifix will also be available
from IBM Service.

Customers who have created independent filesets, even if the filesets are now deleted, are requested to not
create or modify GPFS ACLs on any file or directory until the IBM Service fix is applied.

Customers who have not created independent filesets are requested to not do so until the IBM Service fix
is applied.

If you are already affected by loss of access to files or directories with ACLs, then you are
requested to call IBM Service and reference this problem. The IBM Service person will walk
you thru a fix for correcting the issue.

Please follow the steps below to determine if your GPFS file system may be susceptible to this issue.

Step 1)

On a system with GPFS running, invoke the mmlsfs command to determine the device names
of all file systems

/usr/lpp/mmfs/bin/mmlsfs all -T

Example output would be in the form:

File system attributes 

for /dev/gpfs: ==================================== flag                   value                      description -------------------    ------------------------   ----------------------------------- -T                     /gpfs                      Default mount point

Step 2)

For each file system device listed in step 1, use the following command to determine if your
system may be affected:

echo desc | /usr/lpp/mmfs/bin/tsdbfs <fs-device> | grep inodeSpaceMask

where <fs-device> is the device output from step 1 (e.g. /dev/gpfs in step 1 output example)

If there is any non-zero value from the output of the command, your system is exposed to the issue.

In the following example, the file system /dev/gpfs is safe (no independent filesets were created) but
files in file system /dev/trouble with ACLs are at risk.

# echo desc | /usr/lpp/mmfs/bin/tsdbfs /dev/trouble | grep inodeSpaceMask inodeSpaceMask 0000000000000100 0000000000000000000000000000000000000000000000000000000100000000   # echo desc | /usr/lpp/mmfs/bin/tsdbfs /dev/gpfs | grep inodeSpaceMask inodeSpaceMask 0000000000000000 0000000000000000000000000000000000000000000000000000000000000000
Updated on 2012-07-10T15:25:11Z at 2012-07-10T15:25:11Z by