PMEMPOOL-DUMP(1)

💾 pmempool-dump — dump user data from persistent memory pool

okay so real talk, this is the page for pmempool-dump, and yes it lives in the PMDK Programmer's Manual, and yes I'm gonna make it make sense for you bestie 🫶

✨ SYNOPSIS ✨

       $ pmempool dump [<options>] <file>

that's it. that's the whole vibe check. 💅

⚠️ NOTE

NOTICE: The libpmemblk and libpmemlog libraries are deprecated since PMDK 1.13.0 release.

so like, they still work, but they're giving "old money, no future" — just be aware, no cap. 😭

🌸 DESCRIPTION 🌸

When you invoke pmempool with the dump command, it dumps user data out of the pool file you specified. The output format can be either binary or hexadecimal.

By default the output format is hexadecimal — that's the starting point, that's the default, periodt. ✨

By default, data gets dumped to standard output. But you can totally dump data to a different file by specifying the -o option. Heads up though: in that case, data will be appended to that file — not overwritten, appended. iykyk, don't get caught lacking. 🙈

Using the -r option you can specify the number of blocks/bytes/data chunks using a special text format. Scroll down to the RANGE section for the deets, bestie. 💖

---

👑 Available options:

• -b, --binary — dump data in binary format. simple as that. 🖤
• -r, --range <range> — the range of the pool file to dump. This can be a number of blocks for blk pool type, or either a number of bytes or a number of data chunks for log pool type. 🎯
• -c, --chunk <size> — size of the chunk for log pool type. See pmemlog_walk(3) in libpmemlog(7) for details. 🧚
• -o, --output <file> — name of the output file. (and remember: it appends! 💀)
• -h, --help — display help message and exit. the classic escape hatch. 🚪✨

---

🎀 RANGE 🎀

Using the -r, --range option it's possible to dump only a range of user data. This section describes the valid format of the <range> string.

You can specify multiple ranges separated by commas — yes, plural, go off. 🔥

• <first>-<last> — all blocks/bytes/data chunks from <first> to <last> will be dumped. inclusive energy. 💖
• -<last> — all blocks/bytes/data chunks up to <last> will be dumped. 🌸
• <first>-** — all blocks/bytes/data chunks starting from <first> will be dumped. 🌈
• <number> — only <number> block/byte/data chunk will be dumped. just the one. main character energy, honestly. 👑

---

🌟 EXAMPLE 🌟

       $ pmempool dump pool.bin

Dump user data from pool.bin file to standard output. iconic, effortless. 💅

       $ pmempool dump -o output.bin -r1,10-100 pool_blk.bin

Dump block number 1 and blocks from 10 to 100 from pool_blk.bin — which contains a pmem blk pool — into the output.bin file. look at those ranges slaying. 🔥

       $ pmempool dump -r 1K-2K pool.bin

Dump data from 1K to 2K from the pool.bin file. (yes, that's the manpage's own spelling — "form" not "from" — we're keeping it, we don't fix, we don't touch, periodt 😭🫶)

---

🦋 SEE ALSO 🦋

• pmempool(1)
• libpmemblk(7)
• libpmemlog(7)
• libpmemobj(7)
• <https://pmem.io>

go read those if you want the full lore, bestie, iykyk 💜

---

okay that's the whole page!! 💖 this was brought to you by PMDK, dated 2023-05-31 — screenshot it, bookmark it, tell your friends, dump responsibly. mwah. 🎀✨🦋