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-10888 Lustre <p>'lctl abort_recovery' doesn't abort recovery between MDTs, because unlike abort recovery on single MDT system which only fail unfinished operations, this may break system consistency, so as a tradeoff, Lustre chose consistency over availability. But there are two major causes if recovery between MDTs doesn't finish, the first is network issue, for this type, we can wait indefinitely for network to recover, while the second is software bug, which is difficult for user to fix manually on backend filesystem.</p> <p>Now lfsck is ready, which can fix inconsistency in the system. So we should provide an option to allow user to abort recovery between MDTs, and then fix inconsistencies.</p> LU-10888

'lctl abort_recovery' allow aborting recovery between MDTs

New Feature Major Resolved Not a Bug Hongchao Zhang Lai Siyao Mon, 9 Apr 2018 07:28:24 +0000 Mon, 25 Nov 2019 20:07:50 +0000 Mon, 15 Jul 2019 12:26:54 +0000 Lustre 2.10.0 Lustre 2.11.0 Tue, 9 Jul 2019 00:00:00 +0000 0 5 <p>I think it's also possible for this lack of MDS-MDS abort_recovery to cause hangs in certain situations.  During some testing at Cray, we had an MDS LBUG that happened during replay on MDS restart, so we tried abort_recovery.  That hung in some complex scenario related to cross MDT communication.  We weren't aware at the time that cross-MDT ops weren't handled by abort recovery, but it seems likely to be related.</p> <p>abort_recovery has been enabled between MDTS, the new requirement of aborting<br/> the recovery between MDTs but not aborting between client/MDT will be implemented<br/> in a new ticket</p> Related LU-11111 LU-11419 LU-12546 Development Epic/Theme DNE DNE2 dne Rank 1|hzzvgn: Rank (Obsolete) 9223372036854775807