LCTL-NODEMAP_ADD_IDMAP(8)

💅 LCTL-NODEMAP_ADD_IDMAP — the Lustre Configuration Utilities era 💅

okay bestie, welcome to the lctl-nodemap_add_idmap(8) page, straight out of the Lustre Configuration Utilities manual. we're doing ID mapping today and honestly? it's giving ✨main character✨.

---

🌸 NAME 🌸

lctl-nodemap_add_idmap — define ID mappings for a nodemap

---

🎀 SYNOPSIS 🎀

lctl nodemap_add_idmap or
lctl nodemap add_idmap --name NODEMAP_NAME --idtype {uid|gid|projid}
                       --idmap CLIENTID[-CLIENTID_END]:FSID[-FSID_END]

two ways to spell it, same slay. pick ur fighter 👑

---

🦋 DESCRIPTION 🦋

so nodemap_add_idmap adds an identity mapping to a nodemap. no cap. any client that's a member of that nodemap will have their users' identities mapped accordingly. like, you come in as one ID, you get seen as another. a whole glow-up, but for numbers 💖

now here's the part where you gotta pay attention, bestie, because it's the technical tea: when offsets are defined on the nodemap, any explicit identity mapping should map to an FSID in the offset range [ 0, offset_limit-1 ]. that's the range. if you don't, the mapped ID would escape offsetting 😭 and we do not want escaping, that's not the vibe.

---

✨ OPTIONS ✨

• --name NODEMAP_NAME — the name of the nodemap that this idmap should be added to. tell it where to live 💅
• --idtype {uid|gid|projid} — either "uid" or "gid" or "projid", depending on if it is a user ID or group ID or project ID that is to be mapped. three choices, one destiny 🫶
• --idmap CLIENTID[-CLIENTID_END]:FSID[-FSID_END] — the identity to map, and what it should be mapped to. the first number is the ID of the user or group as it is on the client, and the second number is the ID that it should map to on the Lustre filesystem. client-side → Lustre-side, a whole transformation arc 🌈

---

🔥 EXAMPLES 🔥

here's the lore, copy-paste ready:

# lctl nodemap_add_idmap --name remotesite --idtype uid --idmap 2001:1001
# lctl nodemap_add_idmap --name remotesite --idtype gid --idmap 2002:1002
# lctl nodemap_add_idmap --name remotesite --idtype projid --idmap 33:1
# lctl nodemap_add_idmap --name othersite --idtype uid --idmap 0-999:9000

see how the last one does 0-999:9000? that's the range syntax eating, literally obsessed 😌

---

💜 AVAILABILITY 💜

lctl nodemap_add_idmap is part of the lustre(7) filesystem package since release 2.6.0. it's been iconic since day one, fr fr.

---

🌟 SEE ALSO 🌟

lustre(7), lctl-nodemap-activate(8), lctl-nodemap-add-offset(8), lctl-nodemap-add-range(8), lctl-nodemap-del(8), lctl-nodemap-del-idmap(8), lctl-nodemap-del-offset(8), lctl-nodemap-del-range(8), lctl-nodemap-modify(8), lctl-nodemap-new(8)

the whole friend group, go say hi 🥰

---

aaaand that's the page! this lil masterpiece is from the Lustre manual, dated 2024-08-14 🎀 go map some IDs, bestie, you got this 💅✨