gfs2_jadd(8)

πŸ“¦
version 3.6.1 Β· 2 versions
  • 3.6.1 Β· debian bookworm, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 3.4.1 Β· ubuntu jammy
, in debian bookworm, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– gfs2_jadd β€” bestie edition πŸ’–

okay so real talk, this one lives in the System Manager's Manual and its whole name is gfs2_jadd(8). it's giving sysadmin but make it cute. let's get into it 🫢


✨ NAME ✨

gfs2_jadd β€” add journals to a gfs2 filesystem πŸŽ€


✨ SYNOPSIS ✨

gfs2_jadd [options] <device|mountpoint> ...

✨ DESCRIPTION ✨

so gfs2_jadd is literally the girl who shows up with extra journals (and a few other per-node files, ngl) and adds them to a gfs2 filesystem. πŸ’… and the way that once she's done, the journal index gets updated so that machines mounting the filesystem will see the newly created journals in addition to the existing ones? iconic. but the machines that are already running in the cluster? they're unaffected, periodt. no notes. ✨

gfs2_jadd must be run on a mounted filesystem. adding journals to unmounted filesystems is not supported, bestie, don't even try it 😭. and here's the cute part: you only need to run gfs2_jadd on one node in the cluster, and the added journals will be visible across the whole cluster. slay. πŸ‘‘

gfs2_jadd must be run as root 🧚 and β€” important β€” gfs2_jadd only updates the journal index at the very end of the process if no error conditions are encountered. otherwise? the filesystem is left in its original state. no harm, no foul, we love a clean rollback πŸ’œ


✨ OPTIONS ✨

  • -c megabytes β€” the initial size of each journal's quota change file πŸ“
  • -D β€” print out debugging information about the filesystem layout. she's nosy and we love her πŸ”
  • -h β€” prints out a short usage message and exits. bye bestie πŸ‘‹
  • -J size β€” the size of the new journals in megabytes. the default is 32MB and the minimum size allowed is 8MB. lowkey important: if journals of different sizes are required, gfs2_jadd will need to be run once for each different size of journal. no shortcuts, sorry babe πŸ’…
  • -j number β€” the number of new journals to add πŸ”’
  • -q β€” be quiet. don't print anything. silent main character energy 🀫
  • -V β€” Version. print version information, then exit 🌈

✨ NOTES ✨

okay so this is the tea 🍡: the journals added by gfs2_jadd are not guaranteed to be laid out contiguously the way they are with mkfs.gfs2(8). so honestly it may be beneficial to performance to just create the filesystem with the required number of journals instead of adding journals later. foresight is the vibe, fr fr πŸ’€


✨ SEE ALSO ✨

mkfs.gfs2(8) gfs2_grow(8) πŸ¦‹


no cap: if you're doing anything destructive or clustering-related, double-check your device names first. this page is not gonna catch your typos for you, bestie 😭

and that's the whole thing, my love πŸ’– that was gfs2_jadd(8) from the System Manager's Manual. go add those journals, you absolute queen πŸ‘‘πŸŒΈ mwah πŸ’‹

πŸ“¦ where this page comes from