[LU-7205] OSP sync RPC could be out of order Created: 24/Sep/15 Updated: 10/Aug/17 Resolved: 02/Oct/15 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.8.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Niu Yawei (Inactive) | Assignee: | Niu Yawei (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Severity: | 3 | ||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
Current Lustre doesn't have a mechanism to make sure the RPCs generated when processing OSP sync log arrive OST in order, so if there are two adjacent & depended records (such as two chown operations) in the log, the RPCs for these two records may arrive OST in wrong order, that leads to unexpected inconsistency or failure. A quick solution could be restricting the inflight RPC to 1, and use OUT to combine many operations in a single RPC. |
| Comments |
| Comment by Gerrit Updater [ 28/Sep/15 ] |
|
Niu Yawei (yawei.niu@intel.com) uploaded a new patch: http://review.whamcloud.com/16651 |
| Comment by Gerrit Updater [ 02/Oct/15 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/16651/ |
| Comment by Joseph Gmitter (Inactive) [ 02/Oct/15 ] |
|
Landed for 2.8.0 |