LCTL-NOD...ET_MODIFY(8)

✨ LCTL-NODEMAP_FILESET_MODIFY 💅

okay bestie, welcome to the lctl nodemap_fileset_modify page (yes the manual is LCTL-NOD...ET_MODIFY(8), don't worry about it, the name got squished by the terminal fr). this is the glow-up command for a fileset you already have — no new filesets here, we're just editing the one that exists. sit down, hydrate, let's go 🫶

---

🌸 NAME 🌸

lctl-nodemap_fileset_modify — literally just glams up an existing fileset of a nodemap. that's it. that's the job.

---

✨ SYNOPSIS ✨

lctl nodemap_fileset_modify --name NODEMAP_NAME --fileset SUBDIRECTORY
                            [--rename|-r NEW_SUBDIRECTORY]
                            [--primary|-p] [--alt|-a] [--rw] [--ro]

look at that lineup, it's giving main character energy 👑

---

💖 DESCRIPTION 💖

so nodemap_fileset_modify changes up the properties of a fileset that already exists inside a nodemap. you find your fileset by its SUBDIRECTORY path, inside the nodemap you name with NODEMAP_NAME. easy peasy.

when you modify a fileset, you can touch three things:

• its path 🛤️
• its type — primary or alternate 👑
• its access permissions — read-write or read-only 🔐

huge heads up: this command cannot move filesets between nodemaps. nope. not happening. no cap. the --name and --fileset options are mandatory, so don't come in here with only half the info and expect slay 💀

and here's the dynamic nodemap tea ☕ — nodemap_fileset_modify can be used with dynamic nodemaps, but:

• filesets in dynamic nodemaps cannot be modified to escape the namespace restrictions imposed by any fileset set on the parent's nodemap 🙈
• read-only filesets on the parent nodemap cannot become read-write on the child nodemap 🚫
• if the parent nodemap has no fileset defined, then the child nodemap can freely modify any fileset — freedom, finally 🌈

---

💅 OPTIONS 💅

• -n, --name NODEMAP_NAME — tells us which nodemap is holding the fileset you wanna modify. mandatory, bestie, don't skip it.
• -f, --fileset SUBDIRECTORY — the path of the fileset you're modifying. also mandatory. yes, both. always. 🫶
• -r, --rename NEW_SUBDIRECTORY — changes the fileset's path to the new subdirectory you specify. two rules though, and they're not optional: the new path must begin with a slash (/), and it cannot yet exist as a fileset of that type on the same nodemap. the audacity of trying to reuse a name, we don't do that ✨
• -p, --primary — converts the fileset to a primary fileset. if it's already primary, this flag does literally nothing (no effect, zero, nada). but here's the catch, and it's a big one: --primary can only convert an alternate fileset to primary if there is currently no primary fileset set on the nodemap. oh and it's mutually exclusive with the --alt option — so pick a side, you can't be both 💀
• -a, --alt — converts the fileset to an alternate fileset. already alternate? then no effect, moving on. this one is mutually exclusive with the --primary option. same rules. choose one 🔥
• --rw — sets the fileset to read-write access mode. if it's already read-write, this flag has no effect (we love a no-op icon). mutually exclusive with the --ro option ⚔️
• --ro — sets the fileset to read-only access mode, which is enforced when the fileset applies for a given SUBDIRECTORY at mount time. if it's already read-only, no effect. mutually exclusive with the --rw option. yeah, again. pick one, we've been over this 💅

---

🎀 EXAMPLES 🎀

rename a fileset. a fileset is unique, so the name alone is enough to find it:

# lctl nodemap_fileset_modify --name tenant1 --fileset '/dir1' --rename '/dir2'

flip a primary fileset into an alternate and vice versa (glow-up, glow-down, glow-up again):

# lctl nodemap_fileset_modify --name tenant1 --fileset '/dir1' --alt
# lctl nodemap_fileset_modify --name tenant1 --fileset '/dir1' --primary

change the access mode to read-only and back to read-write:

# lctl nodemap_fileset_modify --name tenant1 --fileset '/dir1' --ro
# lctl nodemap_fileset_modify --name tenant1 --fileset '/dir1' --rw

combine ALL the options to change a fileset's path, type, and access mode in one go. so we're renaming a primary fileset '/dir1' to '/dir2', converting it to an alternate fileset, and setting it to read-only:

# lctl nodemap_fileset_modify --name tenant1 --fileset '/dir1' --rename '/dir2' --alt --ro

one command, three transformations. that's the whole vibe check and it passed 🔥

---

🌈 AVAILABILITY 🌈

lctl nodemap_fileset_modify has been part of the lustre(7) filesystem package since release 2.17.0. iconic since day one, basically 👑

---

👀 SEE ALSO 👀

lustre(7), lctl-nodemap-fileset-add(8), lctl-nodemap-fileset-del(8) lctl-nodemap-new(8),

(go read those too, they're the friend group. this one's the editor, they're the creators and the deleters 🫶)

---

okay that's the whole page, you ate it, no crumbs left 💖 and for the record this gorgeous thing is from Lustre, dated 2025-06-18 — so yes, fairly fresh, very much serving. now go modify some filesets responsibly, bestie. periodt ✨🦋🌸