https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-2396 Lustre <p>The per-ofd and per-export brw_stats are not maintained although the proc files still exist (see /proc/fs/lustre/obdfilter/<b>/brw_stats and /proc/fs/lustre/obdfilter/</b>/exports/*/brw_stats). Since filter_iobuf is now osd_iobuf, down one layer and without access to the export, it would be difficult to restore maintenance of these files.</p> <p>The per-ofd brw_stats file could be replaced with a symlink to ../../osd-whatever/whoever/brw_stats (as in the patch for <a href="https://jira.whamcloud.com/browse/LU-2358" title="LBUG reading /proc/fs/lustre/mgs/MGS/fstype" class="issue-link" data-issue-key="LU-2358"><del>LU-2358</del></a>) but there doesn't seem to be consensus that doing so is the Right Thing.</p> LU-2396

ofd brw_stats not maintained

Bug Minor Resolved Fixed Keith Mannthey John Hammond ofd patch procfs Tue, 27 Nov 2012 16:01:05 +0000 Wed, 8 May 2013 23:30:15 +0000 Fri, 22 Mar 2013 19:00:15 +0000 Lustre 2.4.0 Lustre 2.4.0 0 5 <p>Please see <a href="http://review.whamcloud.com/4689" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/4689</a>.</p> <p>Alex, what do you think about symlinking the brw_stats from the old location in /proc/fs/lustre/obdfilter/*/brw_stats to osd?</p> <p>My preference would be that we DO have the symlink, so that tools that monitor these stats can find them in the same place at least across a couple of releases, and eventually they can move to get the stats from osd&#45;* once there are a few versions that have them there.</p> <p>Moving forward, I'd prefer to break up brw_stats into separate stats files, or at least transform it into YAML that can be parsed more easily, since the ASCII art layout is a mess for parsing.</p> <p>I'm fine with few symlinks from obdfilter to osd. this is already proven to be clear and trivial to implement.</p> <p>hm, just read more carefully.. symlinks to export per-ofd stats are trivial, but John's question was also about per-export brw_stats and I agree it won't be that trivial to maintain. Andreas, do you think we need to preserve per-export brw_stats?</p> <p>Alex, do you think that adding and removing a symlink in the per-export directory is more complex than adding it for the whole device? Something like "../osd/exports/</p> {nid} <p>/brw_stats" for each ofd export. </p> <p>I agree that it is less critical than the main brw_stats, but I have no idea how much these files are used or not. </p> <p>Landed for 2.4</p> Related LU-3300 Development Rank 1|hzvcx3: Rank (Obsolete) 5686 Severity