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-16435 Lustre <p>The mgc_llog_local_copy() does two-step backup of llogs:</p> <ol> <li>local copy to a temporary file</li> <li>remote llog to local copy</li> </ol> <p>though failure in either one are ignored and doesn't prevent mount the reason of failure can be corrupted local copy which will cause mount failure later while being processed.</p> <p>To prevent that the <tt>mgs_llog_local_copy()</tt> should delete local copy if first backup failed due to any reason</p> LU-16435

don't keep bad local copies of config llogs

Improvement Minor Resolved Not a Bug Mikhail Pershin Mikhail Pershin Wed, 28 Dec 2022 08:56:01 +0000 Tue, 17 Jan 2023 13:43:09 +0000 Tue, 17 Jan 2023 13:43:09 +0000 0 3 <p>While making patch and test for the situation I have found that problem is resolved already in all Lustre current versions. The reason of issue was corrupted local copy of config llog which was still used for processing. Right now the latest code doesn't use local config if it is corrupted but ask for remote llog and even when it is being processed such corruption are skipped due to series of recent patches and mount is not failed. There are still possibilities of more severe corruptions like llog header damage, but such can't be handled by Lustre means, e.g. llog_erase() will just not work, etc. In such cases llogs are to be removed by using <tt>debugfs/tunefs</tt> or local FS mount access</p> <p>Not a bug nowadays</p> Related Development Rank 1|i038q7: Rank (Obsolete) 9223372036854775807