[lustre-discuss] How to find the performance degrade reason

Cameron Harr harr1 at llnl.gov
Wed Sep 12 16:17:39 PDT 2018


I realize I didn't answer all the questions, so:

1) For a file-system-level view, we use ltop, a handy utility that's in 
the LMT package (https://github.com/LLNL/lmt). If you want to pinpoint 
OST or MDT tests, you could lock a file/dir to a particular OST/MDT and 
then use 'zpool iostat ...' to monitor I/O for that device

2) Again, I'd recommend getting ltop. 'zpool iostat' can give you 
numerous performance statistics as well.


On 09/12/2018 04:11 PM, Cameron Harr wrote:
>
> Use 'zpool iostat -v ...'. You can review the man page for lots of 
> options, including latency statistics.
>
> Cameron
>
>
> On 09/10/2018 11:21 AM, Zeeshan Ali Shah wrote:
>> Dear All,
>>
>> Suddenly our lustre installation become dead slow, copying data from 
>> local source to lustre result around 20MB/sec before it was above 600 MB.
>>
>> i checked zfs status -xv and (all pool healths are ok)
>>
>> 1) How to check which OSTs are involved during data write operation ?
>> 2) How to check Meta data (read and write) stats ?
>> 3) any other advice to drill down the reason ..
>>
>>
>> /Zeeshan
>>
>>
>> _______________________________________________
>> lustre-discuss mailing list
>> lustre-discuss at lists.lustre.org
>> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
>
>
>
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20180912/51d80bba/attachment-0001.html>


More information about the lustre-discuss mailing list