CLEVIS-LUKS-REPORT(1)

✨ CLEVIS-LUKS-REPORT ✨

okay bestie, welcome to clevis-luks-report 💖 — a lil command from the clevis-luks-report(1) manual that literally just tells you the tea about whether a pin bound to a LUKS1 or LUKS2 volume has been rotated. yes, that's the whole job. and honestly? she ate. 👑

---

🌸 NAME 🌸

clevis-luks-report — reports whether a pin bound to a LUKS1 or LUKS2 volume has been rotated 🔄

---

🎀 SYNOPSIS 🎀

clevis luks report -d DEV -s SLT

---

🦋 OVERVIEW 🦋

so the clevis luks report command takes one lil slot of a LUKS device and checks it — then reports whether the pin bound to it, if any, has been rotated. that's it. that's the vibe. no cap. 💅

---

✨ OPTIONS ✨

• -d DEV — the bound LUKS device, i.e. the device you're investigating 🕵️♀️
• -s SLT — the slot (aka key slot) number for the pin to be verified 🔢
• -q — quiet mode 🌙 if you use it, we will not prompt whether to regenerate the binding with clevis luks regen (which, yeah, that's the thing she'd normally bug you about)
• -r — regenerates LUKS metadata with clevis luks regen -q -d DEV -s SLT ♻️

---

🌈 EXAMPLE 🌈

check whether the pin bound to slot 1 in /dev/sda1 has been rotated:

# clevis luks report -d /dev/sda1 -s 1

like, boom, instant answer bestie 🍓

---

👑 SEE ALSO 👑

• clevis-luks-regen(1)

---

mwah 💋 that's the whole page! this lil love letter lives in the CLEVIS-LUKS-REPORT(1) manual, dated 10/16/2026 — same title, same name, just with way more sparkle 🧚✨