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-587 Lustre <p>after hard reset mgs configuration llog can truncated. in case OST config llog also corrupted it's prevent ost to be started. Same situation can be occurred with MDT also.<br/> it's easy replicated by truncate mgs config llog to zero.<br/> In that case mgs have bit set - 'that target registered' and forbid to re-register target, but none configuration send to OST.</p> lustre 2.1/RHEL6 LU-587

mgs have corrupted config llog but forbid to re-register a target

Bug Minor Closed Incomplete Andreas Dilger Alexey Lyashkov Wed, 10 Aug 2011 07:30:36 +0000 Fri, 28 Oct 2011 10:19:46 +0000 Fri, 28 Oct 2011 10:19:46 +0000 0 2 <p>Shadow, can you please resubmit your patch - <a href="http://review.whamcloud.com/#change,1209" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,1209</a> - again (after merging with current master so that the hash changes). Unfortunately it was submitted at unfortunate time where our testing infrastructure was having problems and os it was not test-built and tested. Thanks</p> <p>Peter,</p> <p>Done <img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p>Thx <img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p>I'm trying to understand this bug and the associated patch, but there is not nearly enough explanation in either to understand what is broken, how it is breaking, or why the patch would fix it. Error messages from the console or kernel debug log would definitely help, as to an explanation of why opening a file read-write would allow it to be corrupted on a hard reset, and why opening it read-only prevents that corruption.</p> <p>Is there a specific test case that causes this corruption? I can't imagine that the local config llog gets corrupted after a hard reset, regardless of the open mode, unless the reset happens immediately after the llog is written and has not yet made it to disk.</p> <p>There isn't any useful information in this bug, or the patch. Closing until some information about how/when this problem is being seen is provided.</p> Development Rank 1|hzvi13: Rank (Obsolete) 6570 Severity