<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Great, thanks!<br>
<br>
Meanwhile the attached patch makes lmt mostly work for me for now with LOCKS, LGR, LCR missing.
<br>
fs/lustre/ldlm/namespaces now in /sys too.<br>
<br>
Part of the issue is that _packed_lustre_version() error return = -1 is not processed in calling functions but is interpreted as packed lustre version ( the version earlier than 0.0.0.0 ).<br>
This causes paths in /proc to be defined like for lustre 1.8.x and this definitely does not work for recent lustre.<br>
Just setting default lustre verstion to 2.10.0 (you can set to 99.999.0.0) makes ltop to work.<br>
I guess lustre versions 1.8 and 2.0 can be dropped because if someone needs these he can take the older distro of ltop.<br>
<br>
The other issue:<br>
lmtmetric succesfully opens "/proc/fs/lustre/version" nine times per run (every time per other two open()) as I can see on my older 2.5.3 system;
<br>
# strace -e open lmtmetric -m mdt 2>&1 | fgrep ' = 3'<br>
18 calls total to open("/proc/fs/lustre/version", ...) out of 35 calls to open("/proc/fs/lustre/...)<br>
Lustre version can be cached.<br>
"/proc/fs/lustre/osd-zfs" is opened four times.<br>
<br>
Best regards, Alex.<br>
<br>
<br>
</div>
</span></font></div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText"><br>
<br>
> On Feb 1, 2018, at 1:37 PM, Di Natale, Giuseppe <dinatale2@llnl.gov> wrote:<br>
> <br>
> Hi Alex,<br>
> <br>
> We are aware of the problem. I'm going to try and develop a patch to handle the move to /sys/ in the next week or so.<br>
> <br>
> Giuseppe<br>
> From: lustre-discuss <lustre-discuss-bounces@lists.lustre.org> on behalf of Alexander I Kulyavtsev <aik@fnal.gov><br>
> Sent: Thursday, February 1, 2018 9:10:20 AM<br>
> To: lustre-discuss@lists.lustre.org<br>
> Subject: [lustre-discuss] ltop for lustre 2.10.2 ?<br>
> <br>
> Is there version of ltop working with lustre 2.10.2 ?<br>
> <br>
> lmtmetric does not work on mds; it is OK checking ost on oss.<br>
> <br>
> # lmtmetric -m mdt<br>
> lmtmetric: error reading lustre MDS uuid from proc: Invalid argument<br>
> lmtmetric: mdt metric: Invalid argument<br>
> <br>
> I suspect it is due to lmtmetric constantly reading /proc/fs/lustre/version and it is now in /sys/...<br>
> <br>
> > [lustre-discuss] missing lustre version in /proc/fs/lustre/version<br>
> > <br>
> > Dilger, Andreas <br>
> > Tue Jun 20 15:34:57 PDT 2017<br>
> > ... skip ...<br>
> > We've had to move a lot of Lustre parameters out of /proc/fs/lustre and into /sys/fs/lustre<br>
> > for most parameter values, or /sys/kernel/debug/lustre (via debugfs) for large statistics<br>
> > due to rules imposed by the upstream kernel developers.<br>
> > ...<br>
> <br>
> I'm trying to get ltop working on SLF 7.4 with lustre 2.10.2. No need for lmt & DB.<br>
> <br>
> Alex.<br>
> _______________________________________________<br>
> lustre-discuss mailing list<br>
> lustre-discuss@lists.lustre.org<br>
> <a href="http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org">http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org</a><br>
<br>
</div>
</span></font></div>
</body>
</html>