gfs2_grow(8)

✨ gfs2_grow(8) ✨

okay bestie, so this is a page from the System Manager's Manual, section 8, and it's all about gfs2_grow — the glow-up tool for your GFS2 filesystem. sit down, grab a strawberry 🍓, let's get into it.

---

💖 NAME 💖

gfs2_grow — expand a GFS2 filesystem 💅

---

🎀 SYNOPSIS 🎀

gfs2_grow [OPTION]... <DEVICE|MOUNTPOINT>...

---

🦋 DESCRIPTION 🦋

so here's the vibe: gfs2_grow expands a GFS2 filesystem, but only after the device the filesystem lives on has itself been expanded. it's giving "second step, not first step" energy, fr fr. what it actually does is grow the GFS2 filesystem so it takes up all that unused space chillin' between where the filesystem currently ends and where the block device ends. 🌸

and once that operation is done, the resource group index for the filesystem gets updated too, so that all the nodes in the cluster can start using the extra storage space that just got added. everybody eats. 👑

heads up: peep lvmlockd(8) for the procedure on how to extend and refresh the logical volume before you run gfs2_grow. do it in that order, bestie, i'm begging 🙈

the DEVICE or MOUNTPOINT arguments have to be paths to mounted filesystems — expanding unmounted filesystems is simply not supported, no cap. and the cute part? gfs2_grow only needs to be run on one node in the cluster. the other nodes will see that the expansion happened and will automatically start using the newly available space on their own. main character energy from one node only, we love to see it. ✨

also: gfs2_grow must be run as the superuser. and when the filesystem can't be resized because of detected errors, gfs2_grow will leave the filesystem in a consistent state. it doesn't leave you in a mess, it leaves you in a state. 💜

---

🌈 OPTIONS 🌈

• -D — print out debugging information about the filesystem layout. 🕵️♀️
• -h — prints out a short usage message and exits.
• -q — be quiet. don't print anything. 🤫
• -K — do not attempt to discard the block device contents. okay so, issuing discards to the device lets some solid state devices and sparse or thin-provisioned storage devices optimise free space. other devices may emulate this behaviour by zeroing the device contents, which can be a slow process. 🐌
• -T — test. do all calculations, but do not write any data to the disk and do not expand the filesystem. this is used to discover what the tool would have done were it run without this flag. this option can be used to display the current state of a mounted GFS2 filesystem. 👀
• -V — version. print out version information, then exit. 🎀

---

🫶 NOTES 🫶

shrinking GFS2 filesystems is currently unsupported. you can grow, you cannot shrink. it's giving one-way street, bestie. 💀

---

⭐ SEE ALSO ⭐

mkfs.gfs2(8) gfs2_jadd(8) lvextend(8) lvmlockd(8)

---

okay that's the whole page, you ate it 🍽️. this was gfs2_grow(8) from the System Manager's Manual — shoutout to that manual and to the gfs2_grow(8) footer sitting at the bottom of the original, iykyk. go forth and expand responsibly, bestie 💖✨🎀🦋🌸💅