[gpfsug-discuss] afmPrepopEnd Callback
Simon Thompson (IT Research Support)
S.J.Thompson at bham.ac.uk
Mon Apr 23 16:08:14 BST 2018
My very unconsidered and unsupported suggestion would be to edit mmfsfuncs on your test cluster and see if it’s actually implemented further in the code 😉
Simon
From: <gpfsug-discuss-bounces at spectrumscale.org> on behalf of "luke.raimbach at googlemail.com" <luke.raimbach at googlemail.com>
Reply-To: "gpfsug-discuss at spectrumscale.org" <gpfsug-discuss at spectrumscale.org>
Date: Monday, 23 April 2018 at 15:11
To: "gpfsug-discuss at spectrumscale.org" <gpfsug-discuss at spectrumscale.org>
Subject: [gpfsug-discuss] afmPrepopEnd Callback
Good Afternoon AFM Experts,
I looked in the manual for afmPreopopEnd event variables I can extract to log something useful after a prefetch event completes. Here is the manual entry:
%prepopAlreadyCachedFiles
Specifies the number of files that are cached.
These number of files are not read into cache
because data is same between cache and home.
However, when I try to install a callback like this, I get the associated error:
# mmaddcallback afmCompletionReport --command /var/mmfs/etc/afmPrepopEnd.sh --event afmPrepopEnd -N afm --parms "%fsName %filesetName %prepopCompletedReads %prepopFailedReads %prepopAlreadyCachedFiles %prepopData"
mmaddcallback: Invalid callback variable "%prepopAlreadyCachedFiles" was specified.
mmaddcallback: Command failed. Examine previous error messages to determine cause.
I have a butcher's in /usr/lpp/mmfs/bin/mmfsfuncs and see only these three %prepop variables listed:
%prepopcompletedreads ) validCallbackVariable="%prepopCompletedReads";;
%prepopfailedreads ) validCallbackVariable="%prepopFailedReads";;
%prepopdata ) validCallbackVariable="%prepopData";;
Is the %prepopAlreadyCachedFiles not implemented? Will it be implemented?
Unusual to see the manual ahead of the code ;)
Cheers,
Luke
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20180423/33c2ccbf/attachment-0002.htm>
More information about the gpfsug-discuss
mailing list