cache_dump(8)

✨ NAME ✨ (cache_dump(8) 🎀)

okay so cache_dump is the tool here, and bestie it's giving "dump cache metadata from a device or file to standard output" 💖 that's the whole job, no cap.

🧚 SYNOPSIS 🧚

cache_dump [options] {device|file}

💅 DESCRIPTION 💅

okay so cache_dump takes the binary cache metadata that the device-mapper cache target made on a device or file and dumps it to standard output in XML format 🫶 it's for analysis or postprocessing, and lowkey iconic for that.

the XML can then be fed into cache_restore to put it back onto a metadata device (so the device-mapper target can process it), or onto a file 🦋

🚫 bestie, this tool cannot be run on live metadata. do NOT try it on live metadata 💀

🎀 OPTIONS 🎀

• -h, --help — print help and exit 🌸
• -V, --version — print version information and exit ✨
• -r, --repair — repair the metadata whilst dumping it 🔥
• -o {xml file} — write the xml to a file you name instead of printing it to stdout 💜

🌈 EXAMPLES 🌈

okay so dumping the cache metadata on logical volume /dev/vg/metadata to standard output in XML format looks like this:

$ cache_dump /dev/vg/metadata

and if you want it repaired while it dumps (same output, to standard output, in XML format), it's giving:

$ cache_dump --repair /dev/vg/metadata

🍓 DIAGNOSTICS 🍓

cache_dump returns an exit code of 0 for success or 1 for error. ngl that's the cleanest vibe check ever 💅

🦋 SEE ALSO 🦋

cache_check(8), cache_repair(8), cache_restore(8) 🫶

👑 AUTHOR 👑

Joe Thornber <ejt@redhat.com>, Heinz Mauelshagen <HeinzM@RedHat.com> — the legends who made this, fr fr 🙈

bestie, that's the whole page 💖 Device Mapper Tools, cache_dump(8) — go slay your metadata 🧚✨