https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-6870 Lustre <p>The llapi changelog internals do not interpret the EOF condition correctly and this breaks 'lfs changelog --follow'.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>t:lustre-release# lctl --device lustre-MDT0000 changelog_register lustre-MDT0000: Registered changelog userid 'cl1' t:lustre-release# touch /mnt/lustre/f0 t:lustre-release# lfs changelog lustre-MDT0000 1 01CREAT 17:28:22.890999977 2015.07.17 0x0 t=[0x200000404:0x36:0x0] j=touch.0 p=[0x200000007:0x1:0x0] f0 2 11CLOSE 17:28:22.896000006 2015.07.17 0x42 t=[0x200000404:0x36:0x0] j=touch.0 t:lustre-release# lfs changelog --follow lustre-MDT0000 1 01CREAT 17:28:22.890999977 2015.07.17 0x0 t=[0x200000404:0x36:0x0] j=touch.0 p=[0x200000007:0x1:0x0] f0 2 11CLOSE 17:28:22.896000006 2015.07.17 0x42 t=[0x200000404:0x36:0x0] j=touch.0 Unknown changelog message type 0:0 Changelog: Protocol error </pre> </div></div> <p>Moreover, since the client side changelogf implementation does not offer blocking reads the llapi handler needs to add a short sleep so that we don't tie up a CPU by spinning on an empty pipe.</p> LU-6870

lfs changelog --follow doesn't work

Bug Minor Open Unresolved WC Triage John Hammond changelog Fri, 17 Jul 2015 17:32:37 +0000 Thu, 14 May 2020 18:32:06 +0000 0 3 Related Development Rank 1|hzxigv: Rank (Obsolete) 9223372036854775807 Severity