[LU-12974] Running lfsck with dry-run (-n) should not move orphan obhect to lost+found Created: 15/Nov/19 Updated: 03/Jul/20 Resolved: 14/May/20 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.10.0, Lustre 2.11.0, Lustre 2.12.0, Lustre 2.13.0 |
| Fix Version/s: | Lustre 2.14.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Lai Siyao | Assignee: | Lai Siyao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Severity: | 3 | ||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
For the OST orphan issue we had reported we had a chance to run lfsck at the maintenance window last month. We ran lfsck with dry-run "-r -n -o", but actually (unexpectedly) it moved orphans to lost+found. It should not fix orphans as it is dry-run. |
| Comments |
| Comment by Peter Jones [ 15/Nov/19 ] |
| Comment by Gerrit Updater [ 14/May/20 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/36767/ |
| Comment by Peter Jones [ 14/May/20 ] |
|
Landed for 2.14 |