dmesg --follow
[ 66243600.000 ] posts.x: Full talk on what's changed in quantization, KV caching, and speculative decoding since Philip's book came out:  |   [ 66243600.000 ] posts.x: A quantization method called TurboQuant promised to shrink the KV cache down to four bits this year, then turned out to cut tokens per second by more…  |   [ 66230100.000 ] posts.x: Curious what The Godfather thinks of this. @HamelHusain  |   [ 66229560.000 ] posts.x: @lukebfox1 This was such a great game! We used to have all-night LAN parties on this one!  |   [ 66229440.000 ] posts.x: Astounding!  |   [ 66179400.000 ] posts.x: Full talk on the harness layers, the files-vs-databases tradeoff, and context rot:  |   [ 66179400.000 ] posts.x: Most of what makes an AI agent reliable has nothing to do with the model itself. In "Total Recall: Agent Memory and Harness Engineering,"…  |   [ 66169620.000 ] posts.x: Full talk on why AI cluster networks need a receiver-driven, message-based protocol instead of TCP:  |   [ 66169620.000 ] posts.x: Most AI clusters still tune their networks for giant weight transfers, but the workloads pushing performance limits now are tiny messages: a KV cache…  |   [ 66168660.000 ] posts.x: Full talk on why llms.txt isn't enough and what actually makes a website agent-ready:  |   [ 66168660.000 ] posts.x: Almost half of the websites in one study already publish an llms.txt file for agents to read, but almost none of the agents actually use it…  |   [ 66166560.000 ] posts.x: @hypeapps @toggl You could still get pretty close. Agent sessions are stored on disk. Subtract the long gaps between your inputs to the session…  |   [ 66166140.000 ] posts.x: @hypeapps @toggl Is this because you’re straddling multiple agent sessions for multiple projects simultaneously?  |   [ 66159420.000 ] posts.x: Full talk on why there's no single right chunk size and how multiscale indexing with RRF closes the gap:  |   [ 66159420.000 ] posts.x: A fixed chunk size is a bet on queries you haven't seen yet. @yuvalinthedeep, Sr. Developer Advocate at AI21, tests that bet in "Stop Chunking Like…  |  
corey@gallon.me:~/til$

Why An 8TB Drive Isn’t 8 Usable TB

FIGURE 1 ⋅ Why An 8TB Drive Isn’t 8 Usable TB

I bought an 8TB external SSD to use as a live boot Linux device. I knew that this issue was due to the way that bits are aggregated into terabytes, but — thanks to our mate ChatGPT — here’s a nice explanation of why my 8TB SSD only shows 7,452.02 GB (7.452TB) of usable space.


The discrepancy between the advertised capacity of your SSD (8 TB) and the actual usable capacity (7,452.02 GB) is due to differences in how storage manufacturers and operating systems calculate disk space. Here’s a detailed explanation:


1. Manufacturer vs. Operating System Measurements

  • Manufacturer Calculation (Decimal - Base 10):
    • Storage manufacturers use the decimal system, where:
      • 1 TB = 1,000,000,000,000 bytes.
      • 8 TB = 8,000,000,000,000 bytes.
  • Operating System Calculation (Binary - Base 2):
    • Operating systems (like Windows, Linux, macOS) use the binary system, where:
      • 1 GiB = 1,073,741,824 bytes.
      • 1 TiB = 1,099,511,627,776 bytes.

When your OS displays capacity:

  • 8,000,000,000,000 bytes ÷ 1,073,741,824 bytes per GiB = ~7,452 GiB.
  • Similarly:
    • 8,000,000,000,000 bytes ÷ 1,099,511,627,776 bytes per TiB = ~7.28 TiB.

2. Why This Happens

  • Marketing: Manufacturers prefer the larger-looking decimal numbers.
  • Reality Check: Computers deal in binary, so the OS displays the actual capacity based on base-2 calculations.

3. Example of Conversion

If you calculate the conversion:

  • Advertised (Decimal): 8 TB = 8,000,000,000,000 bytes.
  • Actual (Binary): 8,000,000,000,000 bytes ÷ 1,073,741,824 (GiB) = ~7,452 GiB.

4. Formatting Overhead

Additionally, after formatting the drive:

  • Some space is used for file system structures and metadata (e.g., NTFS, exFAT, ext4), reducing the usable capacity further.

5. Practical Impact

  • The actual capacity you see (7,452.02 GB) is correct and normal for an 8 TB SSD.
  • You haven’t lost any capacity—it’s just how the numbers are calculated and represented.
corey@gallon.me:~$ tail -f /writing Attach to the stream. An email when I have something worth sending. Replies encouraged!
corey@gallon.me:~$ ls -lt /til ↑2024-11-28 Copying Files in Linux With a Progress Bar
▸2024-11-28 Why An 8TB Drive Isn’t 8 Usable TB ⋅ you are here
↓2024-11-14 Wrap with HTML tags in VSCode