Bug 1268297 - Obsolete disk.dev metric references
Summary: Obsolete disk.dev metric references
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pcp
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nathan Scott
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-02 13:13 UTC by Marko Myllynen
Modified: 2016-07-19 18:05 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 18:05:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Marko Myllynen 2015-10-02 13:13:11 UTC
Description of problem:
pmprobe(1) and man/html/howto.diskperf.html refer both to disk.dev.{active,response} which seem not to be present (on Linux, at least) any more. Perhaps these could be removed or replaced with the modern replacements. Thanks.

Version-Release number of selected component (if applicable):
pcp-3.10.6

Comment 1 Marko Myllynen 2015-10-02 13:22:30 UTC
While at it, howto.diskperf.html talks about metric availability from the IRIX kernel, perhaps this could updated for Linux as well.

Comment 2 Mark Goodwin 2016-04-15 02:02:20 UTC
Hi Marko, the whole howto.diskperf.html needs a revamp (new tools, obsolete metrics, IRIX refs, etc), which has been sort of on my plate for a while now ...

Comment 3 Fedora End Of Life 2016-07-19 18:05:44 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.