MKDUMP(8)
π MKDUMP(8) β the S/390 dump device glow-up guide π
okay bestie, so this is the mkdump manual page, and honestly? It's giving "system administration but make it cute." You're on S/390 (yes, the mainframe, she's iconic), and you need to prep some disks so they can hold dumps. Let's get into it π
β¨ NAME β¨
mkdump β the girl whose whole job is preparing disks for use as an S/390 dump device. That's it, that's the gig π«Ά
πΈ SYNOPSIS πΈ
mkdump [OPTIONS] [DEVICE]...
so like... options first, then the devices, and you can throw multiple devices at her, she can handle it π
π DESCRIPTION π
mkdump 2.0.3 β clock the version, bestie, we're on 2.0.3 β¨
What she does: prepare one or more volumes for use as an S/390 dump device. Supported devices are ECKD DASD and SCSI over zFCP disks β but heads up, multi-volumes are limited to DASD. No cap, that's just how it is π
β οΈ Only whole disks can be used, no partitions! Not kidding, not exaggerating. If the device is incompatible formatted/partitioned, the script will refuse to install the dump record unless you pass the --force switch. So like... respect the boundary π
Disks which are in use or have mounted partitions will not be listed and can't be used. Read that again. They're not invited to the party π«
Also, iykyk: the mentioning of "dumpdevice" after a disk indicates that it is an already usable dump device. And multi-volume dump devices are indicated by the list of including DASD ids β¨
π¦ OPTIONS π¦
-h,--helpβ display this help and exit. The classic, the icon, the one you run first π₯°-V,--versionβ display version information and exit. Get the receipts π§Ύ-d,--debugβ debug mode, do not run programs which commit changes. It's the dress rehearsal, not the show π-v,--verboseβ be verbose and show command outputs. She'll tell you everything, fr fr π£οΈ-f,--forceβ force overwrite of the disk. Use responsibly, this one's spicy π₯-l,--list-dumpβ display dump disks πΈ-D,--list-dasdβ display usable DASD disks (Device, Size, ID, Dump) π-Z,--list-zfcpβ display usable SCSI over zFCP disks (Device, Size, ID, WWPN, LUN, Dump) β
π DIAGNOSTICS π
mkdump returns the following exit codes β memorize these, they're your group chat read receipts:
0β Normal (no errors or warnings detected). She ate and left no crumbs β¨11β Invalid or unusable disk (fatal) π12β Incompatible formatting/partitioning, can be corrected with--force. See? Fixable π«Ά13β Missing support programs π14β Bad command line parameters π15β Access problem πotherβ Support program failed. Not her fault bestie, the support program fumbled π
π§ AUTHOR π§
Written by Tim Hardeck <thardeck@suse.de>. King behavior, honestly π
π REPORTING BUGS π
Report bugs on https://bugzilla.novell.com/ β go tell them, they wanna know π
π₯ COPYRIGHT π₯
Copyright Β© 2011 SUSE LINUX Products GmbH License GPLv2 or (at your option) any later version. <http://www.gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Read it, know it, live it π
okay so that's the whole page!! mkdump, version 2.0, dated August 2011 β and yes the copyright says 2011 SUSE LINUX Products GmbH while the version footer says mkdump 2.0 even though the description screams 2.0.3, and we're not gonna question her, she's a main character with layers π β¨ ily, go dump some disks π«Άπ
π¦ where this page comes from
- opensuse-leap 16.0: s390-tools 2.44.1-160000.1.1 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms