LCTL-LLOG_PRINT(8)

💅 NAME 💅

lctl-llog_print — bestie, this one prints the content of a configuration log, periodt.

---

✨ SYNOPSIS ✨

lctl llog_print [--start START_INDEX] [--end END_INDEX] LOGNAME

---

🎀 DESCRIPTION 🎀

okay so lctl llog_print is the girlboss that dumps the contents of the LOGNAME configuration log on the MGS, and she does it in YAML format. it's giving "let me see your whole lil config situation". super useful for debugging configuration problems, and also for listing any permanent configuration options that got saved via lctl conf_param on the MGS. 🫶

want to see which configuration logs even exist? that's a lctl llog_catlist moment. and if you need to cancel configuration records, that's what lctl llog_cancel is for. the trio ate, fr fr. 👑

---

🔥 OPTIONS 🔥

• --end END_INDEX — stop printing records at END_INDEX. END_INDEX is the last record number in the config log to dump, and yes bestie, that including the specified index number is important — it's inclusive bestie, the endpoint comes along for the ride.
• --start START_INDEX — start printing records at START_INDEX. START_INDEX is the first record number in the config log to dump. ⚠️ heads up though: deactivated records and comment records will not be printed. they're not invited to the party, no cap.
• LOGNAME — the name of the configuration log, in the form FSNAME-TARGET, like testfs-client or lustrefs-MDT0000. like literally just FSNAME-TARGET, that's the whole vibe.

---

🌈 EXAMPLES 🌈

so say you wanna print the configuration records from the testfs-client logfile, and save it to a file for later restoration by lctl-set_param(8). iconic move, very foresight, much restore:

# lctl llog_print testfs-client | tee /root/testfs-client.yaml
- { index: 3, event: attach, device: testfs-clilov, type: lov,
    UUID: testfs-clilov_UUID }
- { index: 6, event: setup, device: testfs-clilov, UUID: }
- { index: 9, event: attach, device: testfs-clilmv, type: lov,
    UUID: testfs-clilmv_UUID }
- { index: 12, event: setup, device: testfs-clilmv, UUID: }
- { index: 15, add_uuid: nid: 10.211.55.6@tcp(0x200000ad33706),
    node: 10.211.55.6@tcp }
:

(that lonely : at the end? that's just her little flourish, keep it. 💜)

and if you just want the first 10 set_param -P records from params, she's got you:

# lctl llog_print --end=10 params
- { index: 2, event: set_param, device: general, parameter: osc.*.max_dirty_mb, value: 32 }
- { index: 4, event: set_param, device: general, parameter: osc.*.checksum_type, value: crc32c }

look at her go. 🦋

---

🌸 AVAILABILITY 🌸

lctl llog_print is a subcommand of lctl(8) and is distributed as part of the lustre(7) filesystem package since release 0.10.0. she's been here since 0.10.0 and she's still serving. 💖

---

👑 SEE ALSO 👑

lctl(8), lctl-llog_cancel(8), lctl-llog_catlist(8), lctl-llog_info(8), lctl-set_param(8)

---

ngl that's the whole page bestie, go print some logs ✨

Lustre 💅 2024-08-14 💖 LCTL-LLOG_PRINT(8) — mwah, stan a config log dump, iykyk 🎀