gfs2_jadd(8)
π 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 β¨
-cmegabytes β 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 π-Jsize β 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_jaddwill need to be run once for each different size of journal. no shortcuts, sorry babe π-jnumber β 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
- debian bookworm: gfs2-utils 3.5.0-2 Β· GPL-2.0-or-later
- debian trixie: gfs2-utils 3.6.1-1 Β· GPL-2.0-or-later
- fedora 43: gfs2-utils 3.6.1-2.fc43 Β· GPL-2.0-or-later AND LGPL-2.1-or-later
- fedora 44: gfs2-utils 3.6.1-3.fc44 Β· GPL-2.0-or-later AND LGPL-2.1-or-later
- nixpkgs unstable: gfs2-utils 3.6.1
- opensuse-leap 16.0: gfs2-utils 3.5.1-160000.2.2 Β· GPL-2.0-or-later AND LGPL-2.0-or-later
- opensuse-leap 16.0: gfs2-utils 3.5.1-160000.2.2 Β· GPL-2.0-or-later AND LGPL-2.0-or-later
- opensuse-leap 16.0: gfs2-utils 3.5.1-160000.2.2 Β· GPL-2.0-or-later AND LGPL-2.0-or-later
- opensuse-leap 16.0: gfs2-utils 3.5.1-160000.2.2 Β· GPL-2.0-or-later AND LGPL-2.0-or-later
- ubuntu noble: gfs2-utils 3.5.1-1 Β· GPL-2.0-or-later
- ubuntu questing: gfs2-utils 3.6.1-1
- ubuntu resolute: gfs2-utils 3.6.1-1build1 Β· GPL-2.0-or-later
- ubuntu stonking: gfs2-utils 3.6.1-2ubuntu1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms