[LU-4940] LFSCK 5: LFSCK needs to tolerate some OSP/OST connection issues Created: 22/Apr/14 Updated: 04/Mar/16 Resolved: 04/Mar/16 |
|
| Status: | Closed |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.6.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | nasf (Inactive) | Assignee: | nasf (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 13653 |
| Description |
|
Currently, the LFSCK fix inconsistent OST-objects via OSP, and if the connection (or the peer) has trouble, related repairing request will return "-ENOTCONN" immediately, then the LFSCK will mark the LFSCK as LF_INCOMPLETE, and move to handle next one. Such model can make the LFSCK to process the inconsistent OST-objects ASAP, but it may cause the LF_INCOMPLETE to be marked too easy, which may be not the best choice. We can consider to make the LFSCK to wait for a while for the connection or peer to recover. |
| Comments |
| Comment by nasf (Inactive) [ 04/Mar/16 ] |
|
The issue has been resolved via the |