[gpfsug-discuss] GPFS RFE promotion

[Sven Oehme]

Ben,

to get lists of 'Hot Files' turn File Heat on , some discussion about it is
here :
https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014920653

thx.  Sven


On Fri, Oct 10, 2014 at 8:26 AM, Ben De Luca <bdeluca at gmail.com> wrote:

> Id like this to see hot files
>
> On Fri, Oct 10, 2014 at 11:08 PM, Bryan Banister <
> bbanister at jumptrading.com> wrote:
>
>> Hmm... I didn't think to use the DMAPI interface.  That could be a nice
>> option.  Has anybody done this already and are there any examples we could
>> look at?
>>
>> Thanks!
>> -Bryan
>>
>> -----Original Message-----
>> From: gpfsug-discuss-bounces at gpfsug.org [mailto:
>> gpfsug-discuss-bounces at gpfsug.org] On Behalf Of Phil Pishioneri
>> Sent: Friday, October 10, 2014 10:04 AM
>> To: gpfsug main discussion list
>> Subject: Re: [gpfsug-discuss] GPFS RFE promotion
>>
>> On 10/9/14 3:31 PM, Bryan Banister wrote:
>> >
>> > Just wanted to pass my GPFS RFE along:
>> >
>> > http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=6
>> > 0458
>> >
>> >
>> > *Description*:
>> >
>> > GPFS File System Manager should provide the option to log all file and
>> > directory operations that occur in a file system, preferably stored in
>> > a TSD (Time Series Database) that could be quickly queried through an
>> > API interface and command line tools.  ...
>> >
>>
>> The rudimentaries for this already exist via the DMAPI interface in GPFS
>> (used by the TSM HSM product). A while ago this was posted to the IBM GPFS
>> DeveloperWorks forum:
>>
>> On 1/3/11 10:27 AM, dWForums wrote:
>> > Author:
>> > AlokK.Dhir
>> >
>> > Message:
>> > We have a proof of concept which uses DMAPI to listens to and passively
>> logs filesystem changes with a non blocking listener.  This log can be used
>> to generate backup sets etc.  Unfortunately, a bug in the current DMAPI
>> keeps this approach from working in the case of certain events.  I am told
>> 3.4.0.3 may contain a fix.  We will gladly share the code once it is
>> working.
>>
>> -Phil
>> _______________________________________________
>> gpfsug-discuss mailing list
>> gpfsug-discuss at gpfsug.org
>> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
>>
>> ________________________________
>>
>> Note: This email is for the confidential use of the named addressee(s)
>> only and may contain proprietary, confidential or privileged information.
>> If you are not the intended recipient, you are hereby notified that any
>> review, dissemination or copying of this email is strictly prohibited, and
>> to please notify the sender immediately and destroy this email and any
>> attachments. Email transmission cannot be guaranteed to be secure or
>> error-free. The Company, therefore, does not make any guarantees as to the
>> completeness or accuracy of this email or any attachments. This email is
>> for informational purposes only and does not constitute a recommendation,
>> offer, request or solicitation of any kind to buy, sell, subscribe, redeem
>> or perform any type of transaction of a financial product.
>> _______________________________________________
>> gpfsug-discuss mailing list
>> gpfsug-discuss at gpfsug.org
>> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
>>
>
>
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at gpfsug.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/20141010/4ca468f9/attachment-0003.htm>