[LU-4891] LFSCK 5: detect inconsistencies at run-time Created: 12/Apr/14 Updated: 04/Mar/16 Resolved: 04/Mar/16 |
|
| Status: | Closed |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Richard Henwood (Inactive) | Assignee: | nasf (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Rank (Obsolete): | 13527 |
| Description |
|
During normal operation, if a inconsistency is discovered, it should be appended to a log to expediate LFSCK operation. |
| Comments |
| Comment by nasf (Inactive) [ 29/Jan/15 ] |
|
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. |
| Comment by nasf (Inactive) [ 04/Mar/16 ] |
|
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. |