Exercise 1: "100% Disk Usage" With Low Transfer Speeds — Possible Solution ==================================================================== WHAT TASK MANAGER'S DISK PERCENTAGE ACTUALLY MEASURES ------------------------------ Per this chapter's own warn-box, "the Disk graph's headline percentage measures active time - the fraction of time the disk had at least one outstanding request - not raw throughput." The 100% figure the user is seeing describes how much of the time window the disk was busy with some request, not how much data was actually being moved during that time. WHY LOW TRANSFER SPEED IS CONSISTENT WITH THIS, NOT CONTRADICTORY ------------------------------ Per this chapter, "a slow drive handling a single, small, queued request can show 100% active time while transferring only a trickle of actual data." A disk can be continuously occupied - always having at least one pending request - while each individual request is small and slow to complete, producing exactly the combination the user is seeing: 100% active time alongside very low actual throughput. The two figures aren't contradictory; they describe genuinely different things. WHY THE "MY DRIVE IS FAILING" ASSUMPTION MAY BE WRONG ------------------------------ Per this chapter, "seeing '100% Disk' and assuming the drive itself has failed, rather than checking the actual MB/s figure right alongside it, is a genuinely common misdiagnosis." A drive can be entirely healthy and still show 100% active time under a workload of many small, queued requests (rather than fewer, larger, fast ones) - this pattern reflects how the disk is being used, not necessarily hardware failure. WHAT SHOULD BE CHECKED INSTEAD OF ASSUMING FAILURE ------------------------------ Rather than concluding drive failure from the percentage alone, the actual MB/s throughput figure displayed right alongside it should be checked - a low throughput figure paired with 100% active time points toward a workload issue (many small requests, a specific process generating them, as this chapter's own worked example later demonstrates) rather than necessarily a hardware problem. WHY THIS WORKS AS AN ANSWER ------------------------------ It explains precisely what the 100% figure measures per this chapter's own warn-box, shows why low throughput doesn't contradict a high active- time percentage, and identifies the specific next step (checking actual MB/s, not assuming failure) this chapter recommends instead.