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-4783 Lustre <p>Params llog was introduced by <a href="https://jira.whamcloud.com/browse/LU-3155" title="Permanent parameters with lctl set_param -P" class="issue-link" data-issue-key="LU-3155"><del>LU-3155</del></a> to use "lctl set_param -P" to set parameters permanently instead of "lctl conf_param". But during investigation on <a href="https://jira.whamcloud.com/browse/LU-3410" title="mgc_copy_llog()) Failed to copy remote log routed1-OST00b3 (-2) ecountered during bring up of a 2.4 file system" class="issue-link" data-issue-key="LU-3410"><del>LU-3410</del></a> I find that when a new filesystem is mounted, params llog won't be created automatically until "set_param -P" is called. So before running "set_param -P", there is no params llog in mgs and the other servers can't make a local copy successfully.<br/> This causes the console error message "LustreError: 13a-8: Failed to get MGS log params and no local copy."is printed.</p> <p>I will push a patch later.</p> LU-4783

start params llog automatically during mgs setup

Bug Minor Resolved Fixed Emoly Liu Emoly Liu Thu, 20 Mar 2014 08:21:13 +0000 Wed, 14 May 2014 22:33:16 +0000 Fri, 9 May 2014 12:02:12 +0000 Lustre 2.5.0 Lustre 2.6.0 Lustre 2.6.0 Lustre 2.5.2 0 7 <p>The patch is at <a href="http://review.whamcloud.com/9737" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/9737</a></p> <p>Landed for 2.6</p> <p>Here is the back-ported patch for Lustre b2_5 branch: <a href="http://review.whamcloud.com/10310" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/10310</a></p> Related LU-3410 Development Rank 1|hzwhv3: Rank (Obsolete) 13161 Severity