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

[Venkateswara R Puvvada]

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.

Regards,
Venkat
-------------------------------------------------------------------
Venkateswara R Puvvada/India/IBM at IBMIN
vpuvvada at in.ibm.com



From:   Loic Tortay <tortay at cc.in2p3.fr>
To:     gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date:   04/16/2016 03:10 PM
Subject:        Re: [gpfsug-discuss] Extended attributes and ACLs with 
AFM-based "NFS   migration"
Sent by:        gpfsug-discuss-bounces at spectrumscale.org



On 16/04/2016 11:23, Venkateswara R Puvvada wrote:
> Hi,
>
> Can you check if AFM was enabled at home cluster using "mmafmconfig
> enable" command? What is the fileset mode are  you using ?
>
Hello,
AFM was enabled for the 2 home filesets/NFS exports with "mmafmconfig 
enable /fs1/zone1" & "mmafmconfig enable /fs1/zone2".

The fileset mode is read-only for botch cache filesets.


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

> Regards,
> Venkat
> -------------------------------------------------------------------
> Venkateswara R Puvvada/India/IBM at IBMIN
> vpuvvada at in.ibm.com
>
>
>
>
> From:   Loic Tortay <tortay at cc.in2p3.fr>
> To:     gpfsug-discuss at spectrumscale.org
> Date:   04/15/2016 09:35 PM
> Subject:        [gpfsug-discuss] Extended attributes and ACLs with
> AFM-based "NFS  migration"
> Sent by:        gpfsug-discuss-bounces at spectrumscale.org
>
>
>
> Hello,
> I have a testbed cluster where I have setup AFM for an incremental NFS
> migration between 2 GPFS filesystems in the same cluster.  This is with
> Spectrum Scale 4.1.1-5 on Linux (CentOS 7).
>
> The documentation states: "On a GPFS data source, AFM moves all user
> extended attributes and ACLs, and file sparseness is maintained."
> (SpectrumScale 4.1.1 Advanced Administration Guide, page 226)
>
> If I'm not mistaken, I have a GPFS data source (since I'm doing a
> migration from GPFS to GPFS).
>
> While file sparseness is mostly maintained, user extended attributes and
> ACLs in the source/home filesystem do not appear to be migrated to the
> target/cache filesystem (same goes for basic tests with ACLs):
>   % getfattr /fs1/zone1/s04/1900/3e479a3eb2eb92d419f812ba1287e8c6269
>   getfattr: Removing leading '/' from absolute path names
>   # file: fs1/zone1/s04/1900/3e479a3eb2eb92d419f812ba1287e8c6269
>   user.mfiles:sha2-256
>   %
> While on the target filesystem:
>   % getfattr /fs2/zone1/s04/1900/3e479a3eb2eb92d419f812ba1287e8c6269
>   %
>
> Am I missing something ?  Is there another meaning to "user extended
> attributes" than OS level extended attributes (i.e. non-GPFS xattr) ?
>



[attachment "smime.p7s" deleted by Venkateswara R Puvvada/India/IBM] 
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160419/f0d07600/attachment-0002.htm>