CDIST-TYPE__FILESYSTEM(7)

📦
version 7.0.0 · 8 versions
, in fedora 43, fedora 44

💾 cdist-type__filesystem 💾

okay bestie, welcome to the cdist-type__filesystem manual page (section 7, if you're keeping track 🎀) — it's the one that makes filesystems happen on your devices, and I'm gonna walk you through it like we're texting at 2am ✨

🌸 NAME 🌸

cdist-type__filesystem — Create Filesystems. yes that's the whole name, no notes 💅

✨ DESCRIPTION ✨

so basically, this cdist type lets you create filesystems on devices. that's the vibe. that's the whole thing 🫶

but hold on, there's rules:

  • If the device is mounted on target, it refuses to do anything. nope. not touching it. it's busy. 🙈
  • If the device has a filesystem that's different from the one you specified, and/or the label isn't correct, it only makes a new filesystem if you've specified the --force option. so without --force, it's just gonna sit there and be like "nah bestie, that's already something" 💀

🔥 REQUIRED PARAMETERS 🔥

you literally cannot skip these, periodt:

  • fstype — the filesystem type. like 'ext3', 'btrfs' or 'xfs'. those exact vibes.

🦋 OPTIONAL PARAMETERS 🦋

these are the ones you can skip, but lowkey why would you:

  • device — the blockdevice for your filesystem. defaults to object_id. on linux, it can be any lsblk accepted device notation, which is iconic honestly.

For example:

/dev/sdx
or /dev/disk/by-xxxx/xxx
or /dev/mapper/xxxx
  • label — the label that should be applied on the filesystem. give it a name, it deserves one 🎀
  • mkfsoptions — additional options that get inserted into the mkfs.xxx call. your extra little seasoning ✨

👑 BOOLEAN PARAMETERS 👑

  • force — normally, this type does nothing if a filesystem is found on the target device. but if you specify force, it's formatted if the filesystem type or label differs from parameters.
Warning: This option can easily lead into data loss! 😭 bestie please, PLEASE back up first. this is not a drill. this is main character energy in the WORST way. data does not come back from that.

💌 MESSAGES 💌

here's what it yells at you when things go right:

  • filesystem <fstype> on <device> : <discoverd device> created — Filesystem was created on <discoverd device>. (yes, <discoverd> is spelled exactly like that in the original, i'm not fixing it, that's canon 💀)

🌈 EXAMPLES 🌈

copy these, they're blessed:

# Ensures that device /dev/sdb is formatted with xfs
__filesystem /dev/sdb --fstype xfs --label Testdisk1
# The same thing with btrfs and disk spezified by pci path to disk 1:0 on vmware
__filesystem dev_sdb --fstype btrfs --device /dev/disk/by-path/pci-0000:0b:00.0-scsi-0:0:0:0 --label Testdisk2
# Make sure that a multipath san device has a filesystem ...
__filesystem dev_sdb --fstype xfs --device /dev/mapper/360060e80432f560050202f22000023ff --label Testdisk3

🫶 AUTHORS 🫶

Daniel Heule <hda--@--sfs.biz> — the icon who made this 💜

📜 COPYING 📜

Copyright (C) 2016 Daniel Heule. Free use of this software is granted under the terms of the GNU General Public License version 3 or any later version (GPLv3+).

ungleich GmbH 2021

and that's the whole page, bestie 💖 this was version 7.0.0 from Jul 31, 2022 — go forth and format responsibly, and fr fr do not touch --force without a backup 🧚✨

📦 where this page comes from