[LU-9959] hsm: cannot schedule two different requests on the same fid Created: 08/Sep/17 Updated: 05/Aug/20 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | CEA | Assignee: | Quentin Bouget |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | HSM | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
mdt_hsm_add_actions() makes the assumption that hsm_find_compatible() will set the hai_cookie field of incoming requests to something other than 0 only if :
The third assumption is used to detect duplicate requests, but hsm_find_compatible() does not exactly work like this. If the incoming request is an ARCHIVE/RESTORE/REMOVE, hsm_find_compatible() will set the hai_cookie field if it finds any request that applies to the same fid. This makes sense in some cases:
But not in others:
|
| Comments |
| Comment by Peter Jones [ 08/Sep/17 ] |
|
Quentin Is this issue something that you are planning to work on or something you are documenting in the hope that someone else will work on it? Peter |
| Comment by Quentin Bouget [ 08/Sep/17 ] |
|
Hi Peter, A little of both. Ben Evans is working on the Quentin |
| Comment by Peter Jones [ 08/Sep/17 ] |
|
In that case I think that it makes sense for you to own this ticket for the time being. I also added a link to |