[LU-5311] LFSCK 4: don't disable creates for all sequences if one bad LAST_ID is found Created: 09/Jul/14 Updated: 28/Sep/14 Resolved: 28/Sep/14 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Andreas Dilger | Assignee: | WC Triage |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 14839 |
| Description |
|
When LFSCK detects a corrupt or missing LAST_ID, it currently disables creates for all sequences, even if this is not necessary: /* Currently, for safe, we do not distinguish which LAST_ID is broken, * we may do that in the future. * Return -ENOSPC until the LAST_ID rebuilt. */ if (unlikely(ofd->ofd_lastid_rebuilding)) GOTO(out_sem, rc = -ENOSPC); However, with multiple MDTs (FID-on-OST) there may be creates in sequences that could continue, or the problem may be in a sequence that have been filled and is no longer in use so there is no value to block all creates. |
| Comments |
| Comment by Alex Zhuravlev [ 09/Jul/14 ] |
|
iirc, there is another ticket (and a way) to improve this - do not block creations at all, just use a different sequence as all we need is unique FID. |
| Comment by nasf (Inactive) [ 28/Sep/14 ] |
|
It will be resolved in LU-5029. |