1 .TH llog_reader 8 "2009 Apr 02" Lustre "System management commands"
3 llog_reader \- lustre on-disk log parsing utility
5 .B "llog_reader filename"
9 parses the binary format of Lustre's on-disk configuration logs.
10 It can only read the logs. Use
14 To examine a log file on a stopped Lustre server, first mount its
15 backing file system as ldiskfs, then use
17 to dump the log file's contents, e.g.
20 mount -t ldiskfs /dev/sda /mnt/mgs
21 llog_reader /mnt/mgs/CONFIGS/tfs-client
24 To examine the same log file on a running Lustre server, use the
25 ldiskfs-enabled debugfs utility (called
27 on some distros) to extract the file, e.g.
30 debugfs -c -R 'dump CONFIGS/tfs-client /tmp/tfs-client' /dev/sda
31 llog_reader /tmp/tfs-client
34 To examine Changelog records on a stopped Lustre server, first mount its
35 backing file system as ldiskfs, then use
37 to dump the log changelog's contents, e.g.
40 # mount -t ldiskfs /dev/sda /mnt/mgs
41 # llog_reader /mnt/mgs/changelog_catalog
42 rec #1 type=1064553b len=64 offset 8192
44 Time : Mon Jan 22 23:28:24 2018
47 -----------------------
49 #01 (064)id=[0x5:0x1:0x0]:0 path=
52 # llog_reader /mnt/mgs/
55 rec #1 type=10660000 len=136 offset 8192
56 rec #2 type=10660000 len=136 offset 8328
57 rec #3 type=10660000 len=128 offset 8464
59 Time : Mon Jan 22 23:30:01 2018
62 -----------------------
63 #01 (136)changelog record id:0x0 cr_flags:0x9000 cr_type:CREAT(0x1)
64 date:'14:30:01.370700741 2018.01.22' target:[0x200000402:0x1:0x0]
65 cr_extra_flags:0x3 user:0:0 nid:10.128.11.159@tcp parent:[0x200000007:0x1:0x0]
69 Although they are stored in the CONFIGS directory, \fImountdata\fR
70 files do not use the config log format and will confuse \fBllog_reader\fR.
72 Lustre Operations Manual, Section 21.1, \fITroubleshooting Lustre\fR.