LFSCK 4: improve LFSCK performance
(LU-6361)
|
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.7.0 |
| Fix Version/s: | Lustre 2.8.0 |
| Type: | Technical task | Priority: | Critical |
| Reporter: | nasf (Inactive) | Assignee: | nasf (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Rank (Obsolete): | 17758 | ||||
| Description |
|
Currently, for every item that is verified by the LFSCK assistant thread, the LFSCK assistant thread will try to locate its parent directory (for namespace LFSCK) or its parent MDT-object (for layout LFSCK) firstly via the given FID. But for most of cases, the system is under consistent status, such object locating is unnecessary. Be as some improvement, we will make the LFSCK to locate related object only when it is really used. |
| Comments |
| Comment by Gerrit Updater [ 06/Mar/15 ] |
|
Fan Yong (fan.yong@intel.com) uploaded a new patch: http://review.whamcloud.com/13993 |
| Comment by Gerrit Updater [ 28/Apr/15 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/13993/ |
[LU-6343]