[gpfsug-discuss] Extended attributes and ACLs with AFM-based "NFS migration"

Loic Tortay tortay at cc.in2p3.fr
Tue Apr 19 14:43:53 BST 2016


On 04/19/2016 08:01 AM, Venkateswara R Puvvada wrote:
> Hi,
> 
> AFM usually logs the following message at gateway node if it cannot open 
> control file to read ACLs/EAs.
> 
>                AFM: Cannot find control file for file system <FS> fileset 
> <Fileset> in the exported file system at home.
>                ACLs and extended attributes will not be synchronized. 
> Sparse files will have zeros written for holes.
> 
> If the above message didn't not appear in logs and  if AFM failed to bring 
> ACLs, this may be a defect. Please open PMR with supporting traces to 
> debug this issue further. Thanks.
> 
Hello,
There is no such message on any node in the test cluster.

I have opened a PMR (50962,650,706), the "gpfs.snap" output is on
ecurep.ibm.com in "/toibm/linux/gpfs.snap.50962.650.706.tar".

BTW, it would probably be useful if "gpfs.snap" avoided doing a "find
/var/mmfs ..." on AFM gateway nodes (or used appropriate find options),
since the NFS mountpoints for AFM are in "/var/mmfs/afm" and their
content is scanned too.
This can be quite time consuming, for instance our test setup has
several million files in the home filesystem.
The "offending" 'find' is the one at line 3014 in the version of
gpfs.snap included with Spectrum Scale 4.1.1-5.


Loïc.
-- 
|       Loïc Tortay <tortay at cc.in2p3.fr> - IN2P3 Computing Centre      |



More information about the gpfsug-discuss mailing list