[gpfsug-discuss] policy ilm features?

[Jan-Frode Myklebust]

I also see that /usr/lpp/mmfs/samples/util/tsinode will list these flags:

[root at scale-dev-01 util]# ./tsinode /mnt/gpfs01/|grep 55559
              55559   631878862      0      0 1048576000  104857600
-rw-r--r--         2 1610965529.234470000 1610965531.035007326
1612952829.394919000      0 blk=1048576 modsnap=1 extperms=0x2,xa
replmeta *illReplicated
unbalanced* dev=3824,150 archive compressed crtime 1610965529.234470000

That program can probably easily be modified to only list these files..


  -jf

On Fri, Feb 19, 2021 at 1:50 PM Jan-Frode Myklebust <janfrode at tanso.net>
wrote:

> We just discussed this a bit internally, and I found "something* that
> might help... There's a mmrestripefs --inode-criteria command that can be
> used to identify files with these unknown-to-ILM flags set. Something like:
>
> # echo illreplicated > criteria
> # mmrestripefs gpfs01 -p --inode-criteria criteria -o result
> Scanning file system metadata, phase 1 ...
>  100 % complete on Thu Feb 18 15:30:10 2021
> Scan completed successfully.
> Scanning file system metadata, phase 2 ...
>  100 % complete on Thu Feb 18 15:30:10 2021
> Scan completed successfully.
> Scanning file system metadata, phase 3 ...
> Scan completed successfully.
> Scanning file system metadata, phase 4 ...
>  100 % complete on Thu Feb 18 15:30:10 2021
> Scan completed successfully.
> Scanning file system metadata, phase 5 ...
>  100 % complete on Thu Feb 18 15:30:10 2021
> Scan completed successfully.
> Scanning user file metadata ...
>  100.00 % complete on Thu Feb 18 15:30:14 2021  (    835584 inodes with total       4271 MB data processed)
> Scan completed successfully.
> Check file '/mnt/gpfs01/result' on scale-dev-01 for inodes with broken disk addresses or failures.
> # cat /mnt/gpfs01/result
> This inode list was generated in the Parallel Inode Traverse on Thu Feb 18 15:30:10 2021
> INODE_NUMBER DUMMY_INFO SNAPSHOT_ID ISGLOBAL_SNAPSHOT INDEPENDENT_FSETID MEMO(INODE_FLAGS FILE_TYPE [ERROR])
>  55559        0:0        0           1                 0                  illreplicated unbalanced REGULAR_FILE
>
> Unclear to me if "-p" is too much work for this task though, or maybe it can be limited with --metadata-only or other options..
>
>
> HTH
>
>
>
>
> On Sat, Jan 20, 2018 at 12:10 AM Edward Wahl <ewahl at osc.edu> wrote:
>
>>
>> This one has been on my list a long time so I figured I'd ask here first
>> before
>> I open an apar or request an enhancement (most likely).
>>
>>  Is there a way using the policy engine to determine the following?
>>
>> -metadata replication total/current
>> -unbalanced file
>>
>> Looking to catch things like this that stand out on my filesystem without
>> having to run several hundred million 'mmlsattr's.
>>
>> metadata replication: 1 max 2
>> flags:                unbalanced
>>
>> Ed
>>
>>
>>
>> --
>>
>> Ed Wahl
>> Ohio Supercomputer Center
>> 614-292-9302
>> _______________________________________________
>> 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/20210219/1fda6425/attachment.htm>