{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreieuf5zdni7websw5quhlf6pehc6bgzjcztymp6cqwlbaydsgftgpq",
    "uri": "at://did:plc:q2k4ilmlzzrnoog5dccpqwor/app.bsky.feed.post/3mn7so2zzvx52"
  },
  "path": "/post/48104717",
  "publishedAt": "2026-05-31T15:22:02.000Z",
  "site": "https://lemmy.ml",
  "tags": [
    "Linux",
    "BigHeadMode",
    "9 comments"
  ],
  "textContent": "submitted by BigHeadMode to linux\n21 points | 9 comments\n\nI ran `compsize` on my debian box. Most files on my btrfs drive are around 20 GB. Almost all are uncompressed. I have 6000 files and 221000 regular extents.\n\nIs that too much fragmentation? The ideal case is 1 extent per file.\n\nI am reading around 100 MiBps from the drive out of a theoretical max of ~119 MiBps on a 1 Gbps line.\n\nedit: On a local read I am getting 130-150 MiBps which exceeds the 1 Gbps network. `pv /path/to/file >/dev/null`\n\nedit 2: For reference, this is a WD Red 6TB drive from around 2018-2020. Max speed should be in the 200 - 250 MBps range.\n\nI defragged a ~300 GB folder and deleted some unneeded files. Extents per file actually went up, but I think that’s because the remaining files are heavily fragmented (many 70+ extents per file). Somewhat surprisingly, most/all of the defragged files still had 3-10 extents. Each file is under 2 GB.\n\nBefore: ~35 extents per file. After: 55 extents per file.\n\n\n    compsize /path/to/folder\n    Processed 2648 files, 145287 regular extents (145287 refs), 1 inline.\n    Type       Perc     Disk Usage   Uncompressed Referenced\n    TOTAL       99%      1.5T         1.5T         1.5T\n    none       100%      1.5T         1.5T         1.5T\n    zstd        19%      236M         1.1G         1.1G\n",
  "title": "Is 35 extents per file too much fragmentation for btrfs?"
}