thin_metadata_size(8)

🎀 thin_metadata_size(8) 🎀

okay so this is the manual page for thin_metadata_size from the System Manager's Manual 💅 bestie, it's the one you need when you're setting up thin provisioning 🦋

🌸 NAME

thin_metadata_size - thin provisioning metadata device/file size calculator. ✨

🧚 SYNOPSIS

thin_metadata_size [options]

💖 DESCRIPTION

okay so thin_metadata_size does the math for you 🧮 it works out how big the thin provisioning metadata needs to be, using the block size of your thin provisioned devices, the size of your thin provisioning pool, and the maximum number of all thin provisioned devices and snapshots added together. ngl this is lowkey important because thin pools hold wildly different stuff, so this tool gives you a sensible starting default size 🫶

👑 OPTIONS

• -h, --help — pop up the help text and exit 🙈
• -V, --version — show the version info and exit ✨
• -b, --block-size {BLOCKSIZE[bskKmMgGtTpPeEzZyY]} — set the block size 🍓

this is the block size of your thin provisioned devices. a plain number means sectors, unless you add a unit. you can use the bytes, sectors, kibibytes, kilobytes, and so on units, either as a one-character suffix or the long form. so -b1m or -b1mebibytes are both giving the same vibe 💅

• -s, --pool-size {POOLSIZE[bskKmMgGtTpPeEzZyY]} — set the pool size 🌊

this is the size of your thin provisioning pool. same deal: plain numbers are sectors unless you tack on a unit like bytes, sectors, kibibytes, kilobytes, and friends.

• -m, --max-thins {count[bskKmMgGtTpPeEzZyY]} — set max thins 🦋

this is the maximum total of all thin provisioned devices and snapshots combined. you can use unit identifiers so you don't have to type a million zeros, like 1000000 can be 1M. a plain number is the exact count.

• -u, --unit {bskKmMgGtTpPeEzZyY} — pick the output unit 🎀

this decides what units the answer comes out in: bytes, sectors, kibibytes, kilobytes, and so on. plain output with no unit specifier is in sectors.

• -n, --numeric-only {short|long} — only show the size number 🔥

this strips the output down to just the number, so you can use it in scripts. short appends the one-character unit specifier, and long appends the unit specifier string.

🌈 EXAMPLES

okay here are the vibes, bestie 🧚

Calculates the thin provisioning metadata device size for block size 64 kibibytes, pool size 1 tebibyte, and a maximum of 1000 thin provisioned devices and snapshots, in sectors with long output:

$ thin_metadata_size -b64k -s1t -m1000

Or, using the long options instead, for block size 1 gibibyte, pool size 1 petabyte, and a maximum of 1 million thin provisioned devices and snapshots, with numeric-only output in gigabytes:

$ thin_metadata_size --block-size=1g --pool-size=1P --max-thins=1M --unit=G --numeric-only

Same as before (1g, 1P, 1M, numeric-only) but with the unit specifier character appended:

$ thin_metadata_size --block-size=1gibi --pool-size=1petabytes --max-thins=1mega --unit=G --numeric-only=short

Or with the unit specifier string appended:

$ thin_metadata_size --block-size=1gibi --pool-size=1petabytes --max-thins=1mega --unit=G -nlong

💀 DIAGNOSTICS

⚠️ bestie, pay attention here: thin_metadata_size returns an exit code of 0 for success, or 1 for error 🙈

🫶 SEE ALSO

thin_dump(8), thin_check(8), thin_repair(8), thin_restore(8), thin_rmap(8) 💜

✨ AUTHOR

Joe Thornber <ejt@redhat.com>, Heinz Mauelshagen <HeinzM@RedHat.com> 👑

---

bestie, that's the whole thing 🦋 this page came from Device Mapper Tools, and you're officially a thin provisioning pro now 💅🌸