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-87 Lustre <p>we hit LBUG in filter_finish_transno() on OSS and OSS got heavy loads, then it went to down, finally. Once rebooted it, then started the recovery, we got same LBUG again. In order to move back into the production, we actually started OST with abort_recov, now it's working well.</p> <p>I found same bug (DDN hit same bug before and filed) on bugzilla (bug 20394) and it should be fixed in 1.8.6. Our branch lustre-1.8.4.ddn2 which based on 1.8.4, but this patch is included and applied to our branch, already. So, I don't know why got same LBUG in filter_finish_transno(). Please investigate this.</p> LU-87

(filter.c:151:filter_finish_transno()) LBUG

Bug Minor Closed Fixed Johann Lombardi Shuichi Ihara Fri, 18 Feb 2011 16:06:35 +0000 Tue, 28 Jun 2011 15:01:42 +0000 Mon, 21 Feb 2011 06:11:34 +0000 Lustre 1.8.6 Lustre 1.8.6 0 4 <p>Please pay attention to bug 24420. It was also about that LBUG. The patch there keeps assertion only on wrong transno assignment but tries to evict client which causes wrong transno order during recovery. This is just workaround but not complete solution because it is stil unclear and looks wrong that transaction ordering can be broken during OSS recovery, but this patch eliminates assertion on wire data at least.</p> <p>The patch we landed for 1.8.6 adds a LASSERT/CERROR to print the values of last_rcvd &amp; lcd_last_transno and i don't see such a message in your logs. Moreover, the line number in the assertion (i.e. filter.c:151) seems to confirm that the patch was not applied.<br/> Are you sure to run a version which has the patch applied? </p> <p>Hi Johann, good to see and talk with you again here <img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p>Sorry, this was my fault and you are correct. The the latest our branch definitely includes this patch. I've just double-checked this. However, the patch applied branch was not used for failed OSS. This is why hit bug20394 on the this customer's OSS. Thanks for Johann for this checking and please close this ticket. </p> <p>Hey Ihara. You are welcomed <img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> Bugzilla ID 20394.0 Development Rank 1|hzw1jr: Rank (Obsolete) 10332 Severity