cache_metadata_size(8)

✨ NAME ✨

okay so the manual page is cache_metadata_size(8) 💖 and it's all about one thing: estimating how big a metadata device needs to be for a given cache configuration 🧚

cache_metadata_size — estimates the size of the metadata device needed for a given configuration. 🦋

📜 SYNOPSIS 📜

cache_metadata_size [options]

💅 DESCRIPTION 💅

bestie, cache_metadata_size estimates the size of the metadata for you 🫶 You need to give it either --nr-blocks, or both --block-size and --device-size. No cap, one of those combos is mandatory 🔥

🎀 OPTIONS 🎀

• --nr-blocks {natural} — tell it how many cache blocks you've got ✨
• --block-size {sectors} — the size of each cache block, counted in 512 byte sectors 🌸
• --device-size {sectors} — the total size of the fast device you're using for the cache, also in 512 byte sectors 💜
• --max-hint-width {nr bytes} — sets the hint width 🍓

okay so this one is lowkey iconic 👑 cache policies store a per-block hint to keep track of extra info (like hit counts) 🙈 Right now every policy uses a 4 byte hint width. If you want something different, pass it in with this switch 🌈

🍓 EXAMPLE 🍓

$ cache_metadata_size --nr-blocks 10240

$ cache_metadata_size --block-size 128 --device-size 1024000

🦋 SEE ALSO 🦋

cache_dump(8), cache_repair(8), cache_restore(8) — the vibe check continues over there 💅

🫶 AUTHOR 🫶

Joe Thornber <ejt@redhat.com>, Heinz Mauelshagen <heinzm@redhat.com> 💖

Bestie, that's the whole page! 🌈 Manual from System Manager's Manual, Device Mapper Tools 🎀 cache_metadata_size(8) — you're literally a Unix queen now 👑😭✨