<span style=" font-size:12pt;font-family:Arial">The short answer is there
is no easy way to determine what file/directory a waiter may be related.
Generally, it is not necessary to know the file/directory since a
properly sized/configured cluster should not have long waiters occurring,
unless there is some type of failure in the cluster. If you were
to capture sufficient information across the cluster you might be able
to work out the file/directory involved in a long waiter but it would take
either trace, or combing through lots of internal data structures.</span><br><br><span style=" font-size:12pt;font-family:Arial">It would be helpful
to know more details about your cluster to provide suggestions for what
may be causing the long waiters. I presume you are seeing them on
a regular basis and would like to understand why they are occurring.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">Regards, The Spectrum
Scale (GPFS) team<br><br>------------------------------------------------------------------------------------------------------------------<br>If you feel that your question can benefit other users of Spectrum
Scale (GPFS), then please post it to the public IBM developerWroks Forum
at </span><a href="https://www.ibm.com/developerworks/community/forums/html/forum?id=11111111-0000-0000-0000-000000000479"><span style=" font-size:10pt;font-family:sans-serif">https://www.ibm.com/developerworks/community/forums/html/forum?id=11111111-0000-0000-0000-000000000479</span></a><span style=" font-size:10pt;font-family:sans-serif">.
<br><br>If your query concerns a potential software error in Spectrum Scale (GPFS)
and you have an IBM software maintenance contract please contact 1-800-237-5511
in the United States or your local IBM Service Center in other countries.
<br><br>The forum is informally monitored as time permits and should not be used
for priority messages to the Spectrum Scale (GPFS) team.</span><br><br><br><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">Damir
Krstic <damir.krstic@gmail.com></span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">gpfsug
main discussion list <gpfsug-discuss@spectrumscale.org></span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">10/10/2019
04:44 PM</span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">[EXTERNAL]
[gpfsug-discuss] waiters and files causing waiters</span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style=" font-size:9pt;font-family:sans-serif">gpfsug-discuss-bounces@spectrumscale.org</span><br><hr noshade><br><br><br><span style=" font-size:12pt">is it possible via some set of mmdiag
--waiters or mmfsadm dump ? to figure out which files or directories access
(whether it's read or write) is causing long-er waiters?</span><br><br><span style=" font-size:12pt">in all my looking i have not been able
to get that information out of various diagnostic commands.</span><br><br><span style=" font-size:12pt">thanks,</span><br><span style=" font-size:12pt">damir</span><tt><span style=" font-size:10pt">_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></span></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><span style=" font-size:10pt">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</span></tt></a><tt><span style=" font-size:10pt"><br></span></tt><br><br><BR>