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-4891 Lustre <p>During normal operation, if a inconsistency is discovered, it should be appended to a log to expediate LFSCK operation.</p> LU-4891

LFSCK 5: detect inconsistencies at run-time

Improvement Minor Closed Won't Fix nasf Richard Henwood Sat, 12 Apr 2014 15:23:45 +0000 Fri, 4 Mar 2016 04:49:27 +0000 Fri, 4 Mar 2016 04:49:27 +0000 0 2 <p>For lookup_by_name case, if the name is there by related MDT-object is lost, then should generate request to the background LFSCK thread to repair such inconsistency.</p> <p>We adjusted the logic for repairing dangling name entry: the default logic is to keep the dangling name entry there and print warning message. It gives the chance to the application to find the issue and avoid losing data silently.</p> Development Rank 1|hzwjyv: Rank (Obsolete) 13527