I would say that the changelog text output format is mainly for debugging and
not really intended as a primary input format for some other changelog
consumer. Instead, the changelog consumer should fetch the binary changelog
records itself and process them directly.
Most of the fields are fairly straight forward:
1 01CREAT 04:24:09.779203918 2024.08.20 0x0 t=[0x2000013a1:0x1:0x0]
j=cp.0 ef=0xf u=0:0 nid=0@lo p=[0x200000007:0x1:0x0] testfile
2 01CREAT 04:26:36.351596347 2024.08.20 0x0 t=[0x2000013a1:0x2:0x0]
j=cp.0 ef=0xf u=0:0 nid=0@lo p=[0x200000007:0x1:0x0] testfile2
3 01CREAT 04:27:54.551053189 2024.08.20 0x0 t=[0x2000013a1:0x4:0x0]
j=cp.0 ef=0xf u=0:0 nid=0@lo p=[0x2000013a1:0x3:0x0] file with spaces
1) record number
2) record type number/name
3) time of update
4) date of update
5) changelog flags
6) t= target FID
7) j= jobid
8) ef= extra field mask
9) u= UID:GID
10) nid= Network ID of node performing update
11) p= parent FID
12) filename (until end of line)
If you think they need more explanation, a patch to lustre/doc/lctl-changelog.1
would be welcome.
On Aug 19, 2024, at 17:30, Michael DiDomenico via lustre-discuss
<lustre-discuss@lists.lustre.org<mailto:lustre-discuss@lists.lustre.org>> wrote:
is there a document somewhere that describes the changelog record line
format? the lustre manual lists the record types, but it doesnt
define what the rest key/value pairs are for each record type. most
of the fields are self evident, but others i'm less clear on.
unfortunately googl'ing 'lustre changelog' doesn't help :(
Cheers, Andreas
--
Andreas Dilger
Lustre Principal Architect
Whamcloud
_______________________________________________
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
